Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: DBMS_JOB sets date to 01/01/4000

Re: DBMS_JOB sets date to 01/01/4000

From: Karen Abgarian <karen.abgarian_at_fmr.com>
Date: Wed, 15 Sep 1999 10:26:33 -0400
Message-ID: <37DFAC98.1B6B5891@fmr.com>


Andreas,

Have you got any explanation for items 1) and 3) or this is just an experience?

Andreas Hundt wrote:

> I had a problem like this. Before using the DBMS_JOB package the
> following conditions must be fulfilled.
>
> 1.) set in the file init.ora resource_limit = FALSE
> 2.) set in the file init.ora JOB_QUEUE_PROCESSES = 2
> 3.) type in ALTER SYSTEM DISABLE RESTRICTED SESSION
>
> Regards Andreas
>
> keaves00_at_my-deja.com schrieb:
>
> > Does anyone know why when I submit a job, even
> > though I have specified the next date and the
> > interval, the date that it is next due to run
> > gets set to January 1st 4000 (midnight)?
> >
> > We have 3 databases -
> > 2 in the UK which work fine and
> > 1 in the States which is giving this problem.
> >
> > Interval is set to 'SYSDATE + 1/1440', i.e. 1
> > minute.
> >
> > Running DBMS_JOB.RUN will set the procedure
> > running, but the date that it will next run is
> > set to 01/01/4000.
> >
> > Thanks.
> >
> > Sent via Deja.com http://www.deja.com/
> > Share what you know. Learn what you don't.
Received on Wed Sep 15 1999 - 09:26:33 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US