Re: Execution interval is incorrect while using DBMS_JOB.SUBMIT

Maoz Mussel wrote:

> Hi,
>
> thank you all for your interest and assistant.
> My conclusion is that DBMS_JOB does not guarantee an exact start time
> for the job, it will run "on or about the scheduled time". So critical
> jobs should be initiated with cronjobs, or other methods more reliable
> than DBMS_JOB mechanism on this perspective.
> One way to get better execution time (to decrease the shifting), is to
> change job_queue_interval parameter value - smaller values will make
> the engine check for jobs to be executed more frequently (though will
> decrease the overhead on Oracle).
>
> See further discussion about the issue in
> http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:13317229864022
>
> Maoz

Your conclusion is incorrect. DBMS_JOB can be made to start at exact times. You just need to think through how you define times as has been shown here many times already this year.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)