RE: set correct "next" time after fixing broken job

You could use LAST_SEC (from dba_jobs) specification for "broken" job, which is "time" portion of LAST_DATE, when you calculate NEXT_DATE for dbms_job.broken.  

Igor Neyman, OCP DBA

ineyman_at_perceptron.com    

-----Original Message-----
Jeffrey Beckstrom
Sent: Tuesday, September 16, 2003 7:39 AM To: Multiple recipients of list ORACLE-L  

If I mark a job as broken to prevent its being run and later mark it as being unbroken, it appears that by default the "next run date" is set as the current date. If I want to have the job rescheduled back to its original date/time, is there a way to do that. Let's say the job runs daily at 10:00 p.m. If I mark the job as broken and later as unbroken without specifying a date, it runs immediately. However, I know that I can code a date when I unbreak the job, but how can I do this in sql without hardcoding a date. We have several jobs we would sometimes like halted during maintenance and would like to avoid having to hardcode a date when unbreak them.  

Jeffrey Beckstrom
Database Administrator
Greater Cleveland Regional Transit Authority 1240 W. 6th Street
Cleveland, Ohio 44113
(216) 781-4204

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Igor Neyman
  INET: ineyman_at_perceptron.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).