Re: dbms_job package

I had a failed job without a broken status because it wasn't really running.

I don't know if that's your problem, but make sure you have the following parameters set in your init.ora

job_queue_processes = 2   (max of 10)
job_queue_interval = 60
job_queue_keep_connections = true

otherwise, Oracle won't even try to run it in the first place.. - Dc.

Connor McDonald wrote:

> serge_l_at_my-deja.com wrote:
> >
> > My problem is: job sent with dbms_job package is failed but don't
> > have a broken status. This is the reason why it rescheduled constantly
> > (not 16 times!).
> > I couldn't resolve the problem and decided to drop and recreate the
> > dbms_job package with dbmsjob.sql script. After that package body is
> > invalid and recompile not help me.
> > 1.What i have to do for recreate the dbms_job package?
> > 2.Why the failed job not broken.
> > Thanks
> > Serge Liberte
> >
> > Sent via Deja.com http://www.deja.com/
> > Share what you know. Learn what you don't.
>
> You need: dbmsjob.sql
> and prvtjob.plb
>
> for both package and package body...
>
> With reference to the failure - does it actually raise an oracle error,
> ie, does the failures count go up...if your job "bombs out" but has an
> exception handler such that the procedure finishes "successfully" then
> the broken flag will not be set...
>
> You can check the snp logs to see if oracle logged any errors with your
> job executions.
>
> HTH
> --
> ===========================================
> Connor McDonald
> "These views mine, no-one elses etc etc"
> connor_mcdonald_at_yahoo.com
>
> "Some days you're the pigeon, and some days you're the statue."
Received on Fri Jun 18 1999 - 11:06:38 CDT