Re: Oracle Job

One thing that can cause job drift is your job_queue_interval setting, which is in seconds. If you have it set to 600 for example, this means Oracle checks what jobs are scheduled every 10 minutes. So, conceivably, depending on other factors, Oracle could wake up 9 minutes and 59 seconds later then you wanted the job to run, and then process when the next scheduled time is at that point, causing drift. To get around this, lower your job_queue_interval to tighten up the schedule, and rather than using sysdate, round it to the nearest hour first before adding 1/12, although I'm not sure off hand at the moment what the syntax for that would be.

• Dc.

On Thu, 27 Apr 2000 21:09:05 GMT, tremblaymartin_at_my-deja.com wrote:

>In article <956834361.356802_at_virtual.nextra.sk>,
> "tony" <bobek_at_ba.ttc.sk> wrote:
>> I have 8.05 on NT and problem are job queues.
>> I created job and next i can run this job but consecutive job it
 isn`t run
>> in periodic time.
>> A long time it was OK. I don`t know what happend.
>> Can you help my anyone?
>> Thanks.
>>
>> Table user_jobs:
>> last_date next_date broken
>> failures
>> 25.4.2000 10:49:36 25.4.2000 12:49:36 N 0
>>
>> command for job:
>> variable jobno number;
>> begin
>> DBMS_JOB.SUBMIT(:jobno
>> ,'pc_mnozstv.i(0,0,1,null);'
>> , SYSDATE
>> ,'SYSDATE + 1/12');
>> commit;
>> end;
>> /
>>
>On Win NT it is not sure that Oracle will start a job on schedule. It
>depends on the workload of the computer. When the workload is low
>Oracle run the job on schedule. When the workload is high Oracle has a
>tendancy to delayed the job. I have seen this behavior quiet often.
>The dbmsjob.sql file describe the job package maybe you can find
>something interesting there.
>>
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
Received on Thu Apr 27 2000 - 00:00:00 CDT