Oracle-L: Re:RE: dbms_job - running jobs every 15 minutes

From: <Jared.Still_at_radisys.com>
Date: Wed, 22 Jan 2003 16:19:24 -0800
Message-ID: <F001.005380AA.20030122161924@fatcity.com>

Oracle does not guarantee that the job will start at the time specified; it seems
that it usually starts about 1 minute later, at least that's what I see.

This would account for the creep, as when the interval is evaluated, it is later
than you might expect.

Jared

JApplewhite_at_austin.isd.tenet.edu
Sent by: root_at_fatcity.com
01/22/2003 11:39 AM
Please respond to ORACLE-L

        To:     Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
        cc: 
        Subject:        Re:RE: dbms_job - running jobs every 15 minutes

Actually, Interval is evaluated at the beginning of the job according to the docs.

I've not seen anyone mention the real cause behind DBMS_Job "creep". That is the setting of Job_Queue_Interval which, by default, is 60 seconds. So your jobs will run 1 minute later each time unless you set Interval to evaluate to an absolute. If someone's set Job_Queue_Interval longer, the "creep" will be longer as well.

Jack C. Applewhite
Database Administrator
Austin Independent School District
Austin, Texas
512.414.9715 (wk)
512.935.5929 (pager)
JApplewhite_at_austin.isd.tenet.edu

                      dgoulet_at_vicr.com  
                      Sent by:                 To:       Multiple 
recipients of list ORACLE-L 
                      root_at_fatcity.com          <ORACLE-L_at_fatcity.com>     
 
                                               cc:   
                                               Subject:  Re:RE: dbms_job - 
running jobs every 15 minutes 
                      01/22/2003 10:34  
                      AM  
                      Please respond to  
                      ORACLE-L

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 at 9:00 AM and
runbs for 5 minutes it's next_date for run #2 will be 9:20, not 9:15, and it
will creep 5 minutes every time.

Dick Goulet
--

Author:
INET: dgoulet_at_vicr.com

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author:
INET: JApplewhite_at_austin.isd.tenet.edu

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services


---------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message

to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author:
INET: Jared.Still_at_radisys.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services


---------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message