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

Home -> Community -> Mailing Lists -> Oracle-L -> DBMS_JOB

DBMS_JOB

From: Dirschel, Steve <Steve.Dirschel_at_bestbuy.com>
Date: Wed, 2 Mar 2005 15:05:59 -0600
Message-ID: <BC335D10F1C0884CB3C3E8AF30D448A8EFB458@rs61mail.na.bestbuy.com>


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
Received on Wed Mar 02 2005 - 16:10:05 CST

Original text of this message

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