Getting ORA-25408 cannot safely replay call on dbms_Scheduler.run_job?

[Stew Stryker]

We're running Oracle 11.2.0.3.0
PL/SQL Developer: 10.0.5.1710

Recently we've started getting the above Oracle error when we try to run a Scheduler job, either from the Scheduler window or from a command window. It's happening consistently.

Yet when we asked our DBA if something was wrong, they said they could run the same command from the same account when they were on the Oracle server or in Oracle's SQL Developer (which they use). It doesn't seem to matter if the job is enabled or not.

We're trying command like this:

BEGIN
dbms_scheduler.run_job(job_name => 'LOAD_DCF_ALUM_SOLICIT');
END;

Suggestions?

Thanks,

Stew

 

[Stew Stryker]

I just read topic # 48584 which suggested trying the SQLPLUS command in a PSD Command Window. I just tried that with the Scheduler command below, but got the same error.

It opened a DOS window to SQL*Plus, ran the command and spat back the error.

[sigh]

 

[IvanZ]

This error is caused by failover switch during transaction. Work it out with DBAs, it has nothing to do with a client.

 

[Stew Stryker]

Ivan,

Thanks for the suggestion. If I understood failover switching better, this might make sense to me.

The little I've read of the documentation suggests that switching only happens when a database fails and transitions to the standby database.

But since, AFAIK, our database is stable, so I wouldn't expect it to be failing over every time I'm trying to submit a job. Our DBAs say that they can run it on the host, which I have no clue how to do.

HOWEVER, I appreciate the nudge. Because of it I found that running the command in SQL Developer's Worksheet window (just for this comparison, I don't use the competitor on a regular basis!), it fails as well, with the error:

Error report -
IO Error: Socket read timed out

So, thank you for the suggestion!

Stew

 

[Stew Stryker]

If anyone cares, this turns out to be a bug with our Junos Pulse VPN server??? Our DBAs are working with the vendor on it.

Oddly, I tried running a job today and it worked twice, but when I logged out and back in, it wouldn't work anymore! Aaagh!

 

[Stew Stryker]

Not to beat a dead horse, but...

A new DBA here picked this issue up again because I'm still getting intermittent problems running a job via PSD's Scheduler, SQL or a Command Line window. It runs fine via Oracle's SQL client.

Here's what the DBA had to say about the matter:

The instances where we've run into problems with programs not able to work properly over the VPN have involved problems with programming in the clients. There are ways to open network connections on the clients that are generally out of date and end up trying to bypass the VPN client. If you run a packet capture on the traffic, the requests will likely come from your local system IP instead of the VPN IP address. These requests will be dropped by the local system once the remote responds to try to set up a TCP connection since network activity should only go over the VPN connection. The security requirements for configuring the VPN software require these non-VPN connections get dropped, so there isn't a good work-around for this.

Is there any possibility this is the case???