Depends...
You may think they don't run when they actually do.
If you have an EXCEPTION routine where you trap the error and don't RAISE it
again, the job will complete successfully.
Have a look at your procedure, and also the column DBA_JOBS.LAST_DATE
--
Syltrem
OpenVMS 7.3-1 + Oracle 8.1.7.4
http://pages.infinit.net/syltrem (OpenVMS related web site, en français)
---zulu is not in my email address---
"Harald Maier" <maierh_at_myself.com> a écrit dans le message de
news:m3llso3f9a.fsf_at_ate.maierh...
> natalia.poggi_at_spm.com.ar (Nat) writes:
>
> > Since our last cold backup something with the dbms_jobs seems to be
> > wrong.
>
> > I cannot figure what. All de jobs are queued in the dba_jobs table
> > with broken = 'N' and failures = null. But for some reason they do
> > not run. They just stay there waiting for the ora_snpXX_sid to picke
> > them up!!!
> >
>
> You might look into the trace files in the directory where the
> 'background_dump_dest' initialization parameter points to. There you
> should find a error message.
>
> Harald
Received on Wed Sep 17 2003 - 12:33:41 CDT
