-
Job just stops running mystery!
9.2, Solaris
I just can't figure out why one particular dbms_job just stops running without any clues?
- The job is hourly
- The job runs successfully for 1 or 2 days every hour
- plenty of job_queue_processes (20)
- it's always the same job
- nothing in the alert log!
- We have a commited insert at the top and bottom of the proc with start and stop time.
.
.
.
BAT_RPT_CA_ORDER_SUMMARY BEGIN 2/11/2003 11:50:04 PM
BAT_RPT_CA_ORDER_SUMMARY END 2/11/2003 11:51:16 PM
BAT_RPT_CA_ORDER_SUMMARY BEGIN 2/12/2003 12:50:03 AM
BAT_RPT_CA_ORDER_SUMMARY END 2/12/2003 12:51:10 AM
THEN IT JUST STOPS!!!
What else can I look for? One thing I not do before I manually ran the job was check failures in DBA_JOBS.
Last edited by gopi; 02-12-2003 at 11:14 AM.
-
Hi,
Look at the dba_jobs.failures -Column, after 18 Times
the Job-Subsystem sets automatically the job broken.
Orca
-
thanx orca,
the very first thing we do when this happens is look in the broken column and it has always been = 'N'
to get the job to run again all i have to do is change the next date.
so mysterious!
-
Originally posted by Orca777
Hi,
Look at the dba_jobs.failures -Column, after 18 Times
the Job-Subsystem sets automatically the job broken.
Orca
18? I think 16.
Oracle Certified Master
Oracle Certified Professional 6i,8i,9i,10g,11g,12c
email: ocp_9i@yahoo.com
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|