Re: DBMS_JOB.SUBMIT

In article <6s6nes0qtomvrbiqnfnl65qv708mp0sjp7_at_4ax.com>,   NeedaHoliday wrote:
> Has anyone ever had a problem of getting job to execute from the
> queue.
>
> Parameter for JOB_QUEUE_PROCESSES is 3
> JOB_QUEUE_INTERVAL is 60.
>
> If I force the job to run using DBMS_JOB.RUN(), everything works
> great. Is there another parm that needed to be modified to turn the
> reader on.
>
> Oracle 7.3.4
>
> REMOVEjames.stewart_at_pwgsc.gc.ca
>
> Omit REMOVE to email
>

Have you remembered to COMMIT; after calling dbms_job.submit? If you do not -- YOU can see the job but the job queue cannot see the job.

Have you checked the NEXT_DATE in the user_jobs table to see that it is what you expect?

Have you checked your alert logs for any errors encountered during the execution of your job?

--
Thomas Kyte                              tkyte_at_us.oracle.com
Oracle Service Industries
http://osi.oracle.com/~tkyte/index.html
--
Opinions are mine and do not necessarily reflect those of Oracle Corp


Sent via Deja.com http://www.deja.com/
Before you buy.