Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORA-01839: date not valid for month specified

user10427867Mar 31 2009 — edited Mar 31 2009
Hi there,

I'm not sure if this is the right place for this posting .... but I got the following errors in my alert log file (10.2.0.1)

Errors in file ..../bdump/xxx_j000_23928.trc
ORA-12012: error on auto execute of job 8888
ORA-01839: date not valid for month specified

in the trace file:
*** ACTION NAME: (AUTO_SPACE_ADVISORY_JOB) 2009-03-30 22:00:02.313
*** MODULE NAME: (DBMS_SCHEDULER) 2009-03-30 22:00:02.313
*** SERVICE NAME: (SYS$USERS) 2009-03-30 22:00:02.313
*** SESSION ID: (194.87) 2009-03-30 22:00:02.313
*** 2009-03-30 22:00:02.313
ORA-12012: error on auto execute of job 8888
ORA-01839: date not valid for month specified

The problem is the date is not valid for month specified, my question is how do I go fix this problem. This is a newly created db.

I only have 2 jobs (select job from dba_jobs) and there is no 8888.

The 2 jobs I have are:

JOB INTERVAL WHAT
1 sysdate+1/240 unlock;
2 trunc(sysdate) + 7 + 3/24 dbms_stats.gather_schema_stats('db_name');


Please assist. Thanks.

Edited by: user10427867 on Mar 31, 2009 12:00 PM
This post has been answered by rbglossip on Mar 31 2009
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 28 2009
Added on Mar 31 2009
6 comments
2,062 views