Re: HELP: DBMS_JOB QUESTION

HI,

this is a common problem when trying to execute jobs based on specific time intervals following the last execution. The job_queue_interval = 60 setting determines how long the SNP process 'sleeps' between catalog checks.
If the SNMP process is busy, or has to contend with other processes etc it will gradually drift away from the desired execution time.

Executing jobs at specific times is much more controllable. For example, to execute every day at 9, you would use
TRUNC(SYSDATE + 1) + 9/24
or even more complicated - every Monday and Tuesday at 9am you would use TRUNC(LEAST(NEXT_DAY(SYSDATE,"MONDAY"),NEXT_DAY(SYSDATE,"TUESDAY"))) + 9 /24 If you must be spot on every 15 minutes then, perhaps you could try running a script via crontab (UNIX) or at (NT) instead.

HTH NeilC

Huiming Li wrote in message <37E736A2.115ABB9E_at_jis.ne.jp>...
>Hi, everybody,
>
>I expect my job to execute automatically every 15 minutes (exactly!).
>Is there a way?
>
>The following is what I have done and the result.
>
>Initialization parameters:
> job_queue_processes = 1
> job_queue_interval = 60
>
>execute dbms_job.submit(:jobno, 'XYZ;', SYSDATE, 'SYSDATE + 1/96');
>
>what I got:
>
> The 1st Time 15:40:13 (expected time 15:40:00)
> The 2nd Time 15:55:40 (expected time 15:55:00)
> The 2nd Time 16:11:20 (expected time 16:10:00)
> ....
>
>It seems that the error is getting larger and larger.
>
>Thanks in advance.
Received on Tue Sep 21 1999 - 03:16:44 CDT