Re: DBMS_JOB sets date to 01/01/4000

From: Andreas Hundt <andreas.hundt_at_merck.de>
Date: Wed, 15 Sep 1999 15:00:20 +0200
Message-ID: <37DF9864.4A17C287@merck.de>

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 - 08:00:20 CDT