| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> RE: DBMS_JOB: Next Date changes
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
Sent via Deja.com http://www.deja.com/ Before you buy. Received on Tue Feb 01 2000 - 14:17:44 CST
 |
 |