How can a broken job "re-enable" itself?
510680May 25 2006 — edited May 25 2006I have noticed that a "broken" job will have re-started itself when I check it the next day. How is this possible?
No one in my group deals with this job, except for me.
There is no other job in any other schema that would enable this job.
I have used both TOAD and the DBMS_JOB package to disable this job. Still, this job refuses to stay broken. Any ideas?