Re: Drift of timing in DBMS jobs

Just to amplify slightly, instead of setting interval to sysdate +1, set it to something like trunc(sysdate)+1/3 . Actually, FWIW (since interval is acually a varchar2) I like to use a format like 'trunc(sysdate) + 08.00/24.00' for readability.

Paul

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:3g3s6u09sca7gvjj09fienmka3qicvpk79_at_4ax.com...
> On 16 Feb 2002 05:00:22 GMT, xux_at_informa.bio.caltech.edu (Xuequn Xu)
> wrote:
>
> >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?
>
>
> Just must have submitted to jobs to run every 24 hour, instead of at
> 08:00 every day sharp.
>
> Hth
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Sat Feb 16 2002 - 07:30:24 CST