Xref: alice comp.databases.oracle.server:56410
Path: alice!news-feed.fnsi.net!netnews.com!dca1-hub1.news.digex.net!intermedia!newscore.univie.ac.at!kanja.arnes.si!not-for-mail
From: jmodic@src.si (Jurij Modic)
Newsgroups: comp.databases.oracle.server
Subject: Re: Job queue Question
Date: Wed, 07 Jul 1999 20:34:25 GMT
Organization: SRC d.o.o, Ljubljana, Slovenia
Lines: 36
Message-ID: <3786b5f0.7111263@news.siol.net>
References: <7m09v5$m3u$1@nnrp1.deja.com> <3788b191.25002091@inet16.us.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Newsreader: Forte Agent 1.5/32.451

On Wed, 07 Jul 1999 20:06:05 GMT, clbeck@us.oracle.com (Christopher
Beck) wrote:

>On Wed, 07 Jul 1999 19:31:48 GMT, amerar@ci.chi.il.us wrote:
>
> ....[SNIP]....
>So basically, your jobs is set to run every 18 hours.  What you want is...
>
>VARIABLE jobno number;
>begin
>  DBMS_JOB.SUBMIT(:jobno,
>                  'cash_man.water_pull;',
>                   trunc( sysdate ) + 18/24,
>                  'sysdate');
                    *******
This is a typo, it should be 'sysdate+1'. However with this type of
interval definition, each subsequent job execution time will be
slightly shifted, depending on the number of job queues and their
"awakening" interval. Over time you might find that your job is
starting around 7 p.m. instead of 6 p.m.

To avoid this you should use an "anchor" in the interval parameter of
a job, e.g.

DBMS_JOB.SUBMIT(:jobno,
                'cash_man.water_pull;',
                 trunc( sysdate ) + 18/24,
                'TRUNC(sysdate) + 1 + 18/24');
                 **************************

Regards,
Jurij Modic <jmodic@src.si>
Certified Oracle DBA (7.3 & 8.0 OCP)
================================================
The above opinions are mine and do not represent
any official standpoints of my employer