Re: DBMS_JOB: Next Date changes

From: Andy Hardy <aph_at_ahardy.demon.co.uk>
Date: Tue, 1 Feb 2000 18:46:56 +0000
Message-ID: <ujDp6HAgoyl4EwXD@ahardy.demon.co.uk>

In article <38970DCA.3477D332_at_us.ibm.com>, Doug Cowles <dcowles_at_us.ibm.com> writes
>I do have a trunc in my next_date, and although the job doesn't slip on a
>daily basis,
>it doesn't execute when it's suppossed to (10:00pm). The job takes less
>than a
>second to run, yet it always exeutes at 10:07pm.
>Have a look at these values for the job:
>LAST_DATE = 31-JAN-00
>LAST_SEC= 22:07:53
>NEXT_DATE = 01-FEB-00
>NEXT_SEC=22:00:00
>
>Yesterday, the values reported were the same (although one day back).
>Why is it always 7 minutes late?

What is your JOB_QUEUE_INTERVAL set to and how many JOB_QUEUE_PROCESSES do you have compared to the number of jobs?

Andy
--
Andy Hardy. PGP key available on request

Received on Tue Feb 01 2000 - 12:46:56 CST