Home » SQL & PL/SQL » SQL & PL/SQL » DBMS_SCHEDULER.RUN_JOB -> ORA-02800: Requests timed out (Oracle 11g)
DBMS_SCHEDULER.RUN_JOB -> ORA-02800: Requests timed out [message #442938] Thu, 11 February 2010 08:58 Go to next message
kregan77
Messages: 21
Registered: January 2007
Junior Member
This is occurring on a coworkers system that I have no access to so please bear with me. We have a job in our system that basically runs in an infinite loop processing a queue (this is significant because we cannot use "use_current_session=>TRUE").

The job was running fine on his system until just last night when he attempted to restart it and got:

ORA-02800: Requests timed out
ORA-06512: at "SYS.DBMS_ISCHED", line 154
ORA-06512: at "SYS.DBMS_SCHEDULER", line 450


The PLSQL that is run is:

begin
  dbms_scheduler.run_job(job_name=>'OUR_JOB', use_current_session=>FALSE); 
end;
/


The job definition looks like this:

BEGIN
        dbms_scheduler.create_job
        (
                job_name        => 'OUR_JOB',
                job_type        => 'STORED_PROCEDURE',
                job_action      => 'XX.SOME_PACKAGE.QUEUE_HANDLER
',
                enabled         => FALSE,
                auto_drop               => FALSE
        );
END;
/

Note that I have used the same exact method to start the job on the same version of the system I have here.

Anybody have any suggestions or ideas? What could cause this to suddenly stop working?

[Updated on: Thu, 11 February 2010 08:59]

Report message to a moderator

Re: DBMS_SCHEDULER.RUN_JOB -> ORA-02800: Requests timed out [message #442939 is a reply to message #442938] Thu, 11 February 2010 09:02 Go to previous messageGo to next message
BlackSwan
Messages: 25049
Registered: January 2009
Location: SoCal
Senior Member
// *Cause:  Some of the requests for asynchronous input or output were not
//          serviced in the required amount of time.
// *Action: If the load on the system is high, it is possible that the
//          timeout limit is too low. Reset it with sfainit(). If the server
//          processes are dying due to unexpected signals, this is an
//          internal error, and ORACLE support should be contacted.


Post Operating System (OS) name & version for DB server system.
Post results of
SELECT * from v$version
Re: DBMS_SCHEDULER.RUN_JOB -> ORA-02800: Requests timed out [message #442940 is a reply to message #442939] Thu, 11 February 2010 09:08 Go to previous messageGo to next message
kregan77
Messages: 21
Registered: January 2007
Junior Member
Thanks, I will try to get that information ASAP. Unfortunately, my coworker for which this problem is occurring is in Australia right now where it's like 2am.
Re: DBMS_SCHEDULER.RUN_JOB -> ORA-02800: Requests timed out [message #442987 is a reply to message #442940] Thu, 11 February 2010 21:31 Go to previous message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Based on the info provided...
I can give you ...

http://oracle-in-steps.blogspot.com/2009/01/ora-02800-when-usecurrentsessionfalse.html

And also
1) verify that your scheduler enabled.
2) Check alert log For any other process causing this error.
3) Check metalink doc,
Quote:
ORA-2800: REQUESTS TIMED OUT WHEN USE_CURRENT_SESSION = FALSE
Doc ID: Note:473551.1

4)It wil be helpful if you post your Oracle version(with 4 digits) and OS with your post.

Good luck

sriram Smile
Previous Topic: Limit number of rows (not what you think)
Next Topic: ORA-01006 w/no binded variables
Goto Forum:
  


Current Time: Fri Dec 09 11:50:42 CST 2016

Total time taken to generate the page: 0.11735 seconds