|
[oracle-l]
||
[Date Prev]
[03-2005 Date Index]
[Date Next]
||
[Thread Prev]
[03-2005 Thread Index]
[Thread Next]
DBMS_JOB
- From: "Dirschel, Steve" <Steve.Dirschel@xxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Wed, 2 Mar 2005 15:05:59 -0600
Oracle 9.2
We want to schedule a job via DBMS_JOB to run at 12:30am and 12:30pm.
I'd prefer to schedule 1 job to do this rather than 1 job to run at
12:30am and 1 job at 12:30pm (I don't want them to run on top of each
other).
When I schedule the job via this command:
execute dbms_job.submit(job=3D>:jobno, what=3D>'program_name;',
next_date=3D>trunc(sysdate+1)+1/48,
interval=3D>'trunc(SYSDATE+12/24,''HH'')');
It works as expected. But the problem I have is if the job gets broken
or the db is down the next time it executes it will schedule itself 12
hours in the future- if it happens to run at 2:10am then the next run
would be 2:00pm. Is there a way with 1 job to force it to only run at
12:30am and 12:30pm regardless of the time of current execution?
Thanks
--
http://www.freelists.org/webpage/oracle-l
|
|
