Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> time shift in sheduled job

time shift in sheduled job

From: James <jialong.x.xie_at_boeing.com>
Date: Tue, 31 Oct 2000 18:59:16 GMT
Message-ID: <G3B640.7Jw@news.boeing.com>

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; Received on Tue Oct 31 2000 - 12:59:16 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US