Re: dbms_job question

Originally posted by Ed Stevens
> I'm just starting to play around with dbms_job, and have another 'what
> am I seeing here' question.
>
> Environment is Oracle 8.1.7.0.0 EE on Solaris v8
>
> The server in question has 2 databases. Yesterday (Wed, April 2) I
> submitted the same job to both databases, thus:
>
> variable jobno number;
> begin
> dbms_job.submit(:jobno,
> 'mvxjdta.refresh_schema_stats;',
> sysdate,
>
> 'TRUNC(LEAST(NEXT_DAY(SYSDATE,''THU''),NEXT_DAY(SYSDATE,''FRI'
> ') )) + 06/24');
> COMMIT;
> END;
>
> This morning (Thurs, Apr 3 06:55) a check of ?????? on one db looks
> exactly like I'd expect. LAST_DATE is 3-Aprl 06:00:35 and NEXT_DATE
> 4-Aprl 06:00:00. However on the other DB I'm seeing LAST_DATE is null
> and NEXT_DATE is 2-Apr 7:13:21. Neither shows any failures and BROKEN
> is 'N'.

It looks like the job in the second database never even tried to run. In the database where the job didn't run, is job_queue_processes set to a non-zero value? This is necessary to start a background process to actually run the job. Also look at job_queue_interval.

HTH,
Patrick

--
Posted via http://dbforums.com