Re: Mysterious Behavior Using DBMS_JOB

In article <37F909A6.440C8A92_at_bates.edu>, Paul Apollo <papollo_at_bates.edu> writes
>I'm trying to schedule a job to run every morning at 5AM. As a test I
>populate a dummy table with SYSDATE when the procedure executes. I set
>the next_date parameter of the DBMS_JOB.SUBMIT command to TRUNC(SYSDATE)
>+ 5/24 and the interval parameter to 'SYSDATE + 1'. I submitted the job
>the evening of 9/28. Here's what I got for output:
>
>DATE_TIME
>9/29/99 5:01:20 AM
>9/30/99 6:01:20 AM
>10/1/99 7:01:20 AM
>10/2/99 8:01:18 AM
>10/3/99 8:01:22 AM
>10/4/99 8:01:24 AM
>
>Two questions:
>
>Why did it skip an hour for three days and then stop skipping the hour
>(and lose 2 seconds)?
>Why didn't the first call take place at 5:00 AM on the 29th?

The job is only submitted to run 'as soon as possible' after 5am - it may be that the job queue was busy with another job at the time.

Andy

>
>I'm new to this package and am asking for your help. TIA
>
>--
>Paul Apollo
>Bates College Information Services
>207-786-6430 Voice 207-753-6901 Fax
>papollo_at_bates.edu
>
>

--
Andy Hardy. PGP key available on request