One potential problem with DBMS_JOBS as is being discussed here is that Oracle
computes the next_date at the end of the job. They do that so that if a job
runs longer than it's schedule interval the two invocations will not run into
each other. Now as discussed, if the job is scheduled to start
...
Jared
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/22/2003 08:34 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re:RE: dbms_job - running jobs every 15 minutes
One potential problem
[EMAIL PROTECTED] [EMAIL PROTECTED]
cc:
Subject: Re:RE: dbms_job - running
jobs every
by: [EMAIL PROTECTED]
01/22/2003 11:39 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re:RE: dbms_job - running jobs every 15 minutes
Actually, Interval is evaluated at the beginning of the job
