| Job [message #38718] |
Wed, 08 May 2002 07:19  |
Fred
Messages: 34
Registered: August 1999
|
Member |
|
|
Hi!
I have this problem; I´m trying to sumbit a job to be excuted every day at 6:23 am; but there´s the wake up agent (ot sth like that), which is set to more than 60 minutes (or so it seems), which "wakes up" and executes the jobs that are pending. Today, several days after the job submission, the "next date" has "moved" to 11:44 am.
My question is: is there a way of submitting a job with the interval parameter to be sth like 'trunc(sysdate+1) || 06:23:00'? So that the wakeup agent doesn´t "move" the expected time of execution?.
Thanks in advance!!!
Fred
|
|
|
|
| Re: Job [message #38723 is a reply to message #38718] |
Wed, 08 May 2002 10:23  |
Todd Barry
Messages: 4819
Registered: August 2001
|
Senior Member |
|
|
The next_date is calculated at the end of your job each time, so if your job takes a while to run, you will see slippage. If you set your interval to:
trunc(sysdate + 1) + (6/24) + (23/(24*60))
the job should start at 6:23am each day.
sql>alter session set nls_date_format = 'dd/mm/yyyy hh:mi:ss am';
Session altered.
sql>select trunc(sysdate + 1) + (6/24) + (23/(24*60)) from dual;
TRUNC(SYSDATE+1)+(6/24
----------------------
09/05/2002 06:23:00 am |
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
