Re: time shift in sheduled job

In our last gripping episode "James" <jialong.x.xie_at_boeing.com> wrote:
> I need to run the scheduled job every two hours. So far so good. But I
> notice that there is a problem because the next_date has been
 shifting from
> the sharp o'clock after a few runs. For example, if I start the job
 at 12:00
> noon, the next job will be running at about 2:01, the next one may be
 4:02.
> I can see that this will become serious after a few months. I can re-
 submit
> the job after a few days. But is there any better way to reset the
 next_date
> to sharp o'clock? Thanks in advance for any clue.
>
> Here is the script:
>
> BEGIN
> DBMS_JOB.ISUBMIT
> (1,'MY_PROC;',TRUNC(SYSDATE)+12/24,'SYSDATE+1/12',NULL);
> COMMIT;
> END;
>
>

Since NEXT_DATE and NEXT_SEC are apparently set at the termination of the current job the duration of the job must be taken into consideration when setting the next time value. I should imagine that you will need to recalculate your constant and make it just slightly less than 1/12 -- you might try 79/960 as a start and sdjusts from there. Your adjustment will need to be just slightly less than 2 hours to hope to hit your 'sharp o'clock' target.

--
David Fitzjarrell
Oracle Certified DBA


Sent via Deja.com http://www.deja.com/
Before you buy.