This content has been marked as final. Show 10 replies
welcome to otn forums.
try with this views:
When a job fails it is automatically re-executed. This is repeated 16 times. After 16 times it is marked as 'broken'.
Dba_jobs will show which jobs are broken.
The dbms_job.broken procedure can unmark them as broken.
All of this, of course, is documented.
Senior Oracle DBA
Remember my db version is 9i and I'm using dmbs_job, I think dba_scheduler is not gonna work.
Thanks btw :)
yes, you are right, i was thinking in 11g...
any error on alert.log?
Edited by: Fran on 20-may-2013 7:49
None of my jobs are broken and the failures are 0.
if no errors at alert.log, please check:
Well, I have checked when the jobs supposed to runned and none message was alerted.
The jobs are working, they were runned automatically before. I think the problem is in execute them at the time I seted.
Result from dba_jobs:
As you can see, the job didn't run at 18/05/13
can you run it manually?1 person found this helpful
check if you have arrived at the maximun job_processes:
sql>sho parameter job_queue_processes
Yes, when the jobs run ok with this:
sql>show parameter job_queue_processes
NAME TYPE VALUE
job_queue_processes integer 100
I think the value 100 it's ok to me.
Any suggestion? I'm kinda lost with this problem
I'm sorry for all this mess! The other guy who work with me changed the value of job_queue_processes to 0 and didn't tell me. At morning I was changing the value to 100 and at night, when the jobs are supposed to run, he changed back to 0. It was a communication failure.
Thanks for all your tips!