Check dba_jobs_running to see if it was already running when you
executed the command.

If you are on Oracle 8.1.7, also check the number of "FAILURES" in
dba_jobs, if this is '16' you might has to bounce the database.

I've had similar issues with replication 'jobs' where if "FAILURES" = 16
I was toast because of some BUG.

Good luck

Jeff

-----Original Message-----
From: oracledba-return-133106-JEFFERY.L.SCHRENK=saic.[Email address protected]
[mailto:oracledba-return-133106-JEFFERY.L.SCHRENK=saic.[Email address protected]
On Behalf Of Qi cheng
Sent: Wednesday, October 04, 2006 11:59 AM
To: LazyDBA Discussion
Subject: ORACLE JUBS STILL BROKEN

after issue: EXECUTE dbms_job.broken(61,FALSE);

the job seems still broken.

Any ideas?

Thanks.



---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


Oracle LazyDBA home page