Re: DBMS_JOB: Next Date changes

You are hostage to the delay between the time requested and the next time the snp process picks up and launches the activity. What you can do is ensure the problem gets no worse by setting the DBMS_JOB interval to for example which ensures a daily job to run every half past ten in the evening.

    /*1:Days*/ TO_DATE(TO_CHAR(TRUNC(SYSDATE)+1,'YY-MON-DD') ||':20:30:00','YY-MON-DD:HH24:MI:SS') Okay so you cannot remove the gap between this time and when the system actually gets it going. You can ensure that a series does not get later and later, day by day.

As others have suggested you can reduce the SNP job process interval or add more processes to speed up the processes of job launch identification and action.

Regards

--
Kevin A Lewis (BOCM PAULS LTD) - Animal Feed Manufacturer - Ipswich United Kingdom)

                        <Kevin_A_Lewis_at_Hotmail.com>

The views expressed herein by the author of this document are not necessarily those of BOCM PAULS Ltd. Frederic Bidon <fbi_at_mobilix.dk> wrote in message news:2D3005375CAED31199D00008C784963F020974_at_ms02.mobilix.dk...
> My opinion is that you can't.
>
> DBMS_JOB uses jobs queues handled by snp process (started according to the
> job_queue_processes parameter).
> Each snp session can handle one job at at time.
> When a snp is idle it scans jobs to be submited every job_queue_interval
> (typically 60 seconds).
>
> If no snp is idle, then the next job has to wait that one snp queue is
free
> to handle it.
>
> The problem is that the next occurence of the job will be calculated
> according to the actual date of execution, hence this "drift" of job
> execution time.
>
> If someone smarter has found a solution, I would be also interested.
> The only way I have found so far is to reschedule on a regular basis my
jobs
> (from a script) to minimize the drift and harness the problem of automatic
> rescheduling when a job fails.
>
> To minimize the pb, you should start several snp processes and set the
> job_queue_interval to a smaller value.
>
> Reagrds,
>
> Frederic.
>
> -----Original Message-----
> From: Richard de Fonseka [mailto:rdefonseka_at_scnet.com.au]
> Sent: 25. januar 2000 18:35
> To: comp.databases.oracle.server_at_list.deja.com
> Subject: DBMS_JOB: Next Date changes
>
>
> Message from the Deja.com forum:
> comp.databases.oracle.server
> Your subscription is set to individual email delivery
>
> I can submit a job to run at exactly 11:00pm:
>
> execute
> dbms_job.isubmit(300,'apl.update_msf600_comparison();',trunc(sysdate)
> + 23/24,'sysdate+1');
>
> When I check ALL_JOBS after the job executes, the Last Date changes
> (e.g. 11:02pm) and the Next Date changes as well.
>
> I have tried to change the Next Date using DBMS_JOB.CHANGE at the end
> of the procedure being executed.
>
> How do I keep the start date/time to exactly 11:00pm.
>
> Thanks,
> Richard
>
>
>
> _____________________________________________________________
> Deja.com: Before you buy.
> http://www.deja.com/
> * To modify or remove your subscription, go to
> http://www.deja.com/edit_sub.xp?group=comp.databases.oracle.server
> * Read this thread at
> http://www.deja.com/thread/%3C388ddd2a.3096492%40news.iinet.net.au%3E
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Fri Feb 04 2000 - 09:52:51 CST