DBMS_JOB sets date to 01/01/4000

From: <keaves00_at_my-deja.com>
Date: Wed, 15 Sep 1999 08:19:27 GMT
Message-ID: <7rnkq8$ec$1@nnrp1.deja.com>

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 - 03:19:27 CDT