I’ve setup jobs very similar as described in by RnR in this post.
2004982
The only difference is that I replaced “dbms_lock.sleep(65);” with an heavyweight procedure that uses most resources on the database server and runs much longer than a min.
So it looks something like this…
begin
dbms_scheduler.create_job
( 'first_job', job_action =>
'insert into job_output values(systimestamp, ''first job begins'');
heavy_weight_prc;
insert into job_output values(systimestamp, ''first job ends'');',
job_type => 'plsql_block',
enabled => false ) ;
dbms_scheduler.set_attribute
( 'first_job' , 'max_run_duration' , interval '60' second);
end;
/
The problem seems that sinper_job doesn’t run when max duration is exceeded because of the heavy load on the database server. Sinper_job runs once heavy_weight_prc is finished.
Please advise on how to make this work properly. How can I ensure sinper_job always runs no matter what the load on database is?
Edited by: Phil on Apr 17, 2013 2:38 PM
Running 11g release 2