I found this problem with jobs submitted by DBMS_JOB:
Say a job is scheduled to run at 8:00 every day, and
the execution of the job takes about 10 minutes. Gradually,
you will find that the start time of the job will drift to
9:00, or even later. The problem is that, the first
execution might be at 8:00 sharp, but the next time it will
start at 8:10, and the next at 8:20, and so on (assume it
takes 10 minutes for the job to finish once). The timing
simply drifts and there is no way to control it, other than
remove and re-schedule the job. Why is that? Shuldn't the DBMS
jobs be as precise in timing as the Unix cron jobs are?
Received on Fri Feb 15 2002 - 23:00:22 CST
