Raj, WARNING: Cron has been known to fail around here leaving one heck of a mess behind. The primary culprit is when you have a power failure. In our case the power failure lasted more than 8 hours. When the computer restarted the cron job's time had passed & it would not start for another week by itself. On the other hand a dbms_job that should have started at about the same time did. We use both, but you have to understand the weaknesses of both.
Dick Goulet ____________________Reply Separator____________________ Author: "Jamadagni; Rajendra" <[EMAIL PROTECTED]> Date: 6/10/2002 10:38 AM We had the same situation and then we use "cron" that never fails. Now, we don't trust dbms_job ... I had a TAR open on that, but can't access it now. Raj ______________________________________________________ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art! -----Original Message----- Sent: Monday, June 10, 2002 2:13 PM To: Multiple recipients of list ORACLE-L Anyone run into any problems with the job scheduler in 9iR1 not kicking off jobs when they are scheduled? We have a situation where a given job (runs every 4 hours or so) will be kicked of successfully 2-3 times, and then on the 4th time the scheduler does not kick it off, next_date is not incremented... it's like the job just gets lost in space...This same scheduled job ran fine in 8i. (this is an 8i to 9i migrated database) Any thoughts on this?
*********************************************************************This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*********************************************************************2