Oracle Jobs scheduled in the past

we had an issue with the scheduled jobs, there is job scheduled to move the listener logs to another 


destination, unfortunately this job was failing for the past few days. Its last successful run was on 15 July. 




This Job's successfull run was on 15th July 2011, the next scheduled run was on 16th July, since the job didn't start on 16th July, the subsequent days it failed.


  1* select job_name,status,REQ_START_DATE from DBA_SCHEDULER_JOB_RUN_DETAILS where

JOB_NAME='MOVE_LISTENER_LOG'order by req_start_date
SQL> /

MOVE_LISTENER_LOG
SUCCEEDED
24-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
25-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
26-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG

SUCCEEDED
27-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
28-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
29-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED

30-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
01-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
02-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
03-JUL-11 09.14.59.000000 AM -08:00


MOVE_LISTENER_LOG
SUCCEEDED
04-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
05-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
06-JUL-11 09.14.59.000000 AM -08:00


MOVE_LISTENER_LOG
SUCCEEDED
07-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
08-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
09-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG

SUCCEEDED
10-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
11-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
12-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED

13-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
14-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
15-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
FAILED
17-JUL-11 12.45.04.863661 PM -08:00


MOVE_LISTENER_LOG
FAILED
17-JUL-11 12.51.15.624930 PM -08:00

MOVE_LISTENER_LOG
FAILED
19-JUL-11 09.49.17.716590 AM -08:00

MOVE_LISTENER_LOG
FAILED
19-JUL-11 09.50.14.282872 AM -08:00


26 rows selected.

when we checked our next run date, it was in the past.(i.e., the sysdate is 24 July) 23 July


SQL> select   JOB_NAME,FAILURE_COUNT,NEXT_RUN_DATE,END_DATE from  dba_scheduler_jobs where job_name='MOVE_LISTENER_LOG';


MOVE_LISTENER_LOG     0    23-JUL-11 09.14.59.600000 AM -08:00


SQL> SELECT owner, job_name, enabled FROM dba_scheduler_jobs where job_name='MOVE_LISTENER_LOG';

DBA_USER
MOVE_LISTENER_LOG
TRUE

SQL> select owner,job_name,ENABLED,state, next_run_date from dba_scheduler_jobs where job_name='MOVE_LISTENER_LOG';

DBA_USER
MOVE_LISTENER_LOG
TRUE            SCHEDULED
23-JUL-11 09.14.59.600000 AM -08:00


SQL> exec dbms_scheduler.run_job(job_name=>'DBA_USER.MOVE_LISTENER_LOG', use_current_session=>FALSE);

PL/SQL procedure successfully completed.

Still the Job didn't start even after force it to run using run_job procedure. It still shows 15th July as the successful run date

SQL> select OWNER,JOB_NAME,STATE,LAST_START_DATE from dba_scheduler_jobs where JOB_NAME='MOVE_LISTENER_LOG';

DBA_USER
MOVE_LISTENER_LOG
SCHEDULED
15-JUL-11 09.14.59.097255 AM -08:00


SQL>  select job_name,status,REQ_START_DATE from DBA_SCHEDULER_JOB_RUN_DETAILS where

JOB_NAME='MOVE_LISTENER_LOG';

MOVE_LISTENER_LOG
FAILED
17-JUL-11 12.51.15.624930 PM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
29-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
01-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG

SUCCEEDED
02-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
03-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
04-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED

05-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
06-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
07-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
08-JUL-11 09.14.59.000000 AM -08:00


MOVE_LISTENER_LOG
SUCCEEDED
09-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
10-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
11-JUL-11 09.14.59.000000 AM -08:00


MOVE_LISTENER_LOG
SUCCEEDED
12-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
13-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
14-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG

SUCCEEDED
15-JUL-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
24-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
25-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED

28-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
26-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
27-JUN-11 09.14.59.000000 AM -08:00

MOVE_LISTENER_LOG
SUCCEEDED
30-JUN-11 09.14.59.000000 AM -08:00


MOVE_LISTENER_LOG
FAILED
17-JUL-11 12.45.04.863661 PM -08:00

MOVE_LISTENER_LOG
FAILED
19-JUL-11 09.49.17.716590 AM -08:00

MOVE_LISTENER_LOG
FAILED
19-JUL-11 09.50.14.282872 AM -08:00


26 rows selected.

SQL> select sysdate from dual;

24-JUL-11

SQL> select   JOB_NAME,FAILURE_COUNT,NEXT_RUN_DATE,END_DATE from  dba_scheduler_jobs where

job_name='MOVE_LISTENER_LOG';


MOVE_LISTENER_LOG     0    23-JUL-11 09.14.59.600000 AM -08:00

The next scheduled date is on 23 Jul-11, that is yesterday. So we need to change the next scheduled time. for that sake, we need to disable and enable the particular job.

-- to Disable a job
exec dbms_scheduler.disable('MOVE_LISTENER_LOG',true);

-- to enable a job
exec dbms_scheduler.enable('MOVE_LISTENER_LOG');



SQL> select owner,job_name,ENABLED,state, next_run_date from dba_scheduler_jobs where

job_name='MOVE_LISTENER_LOG';

OWNER   JOB_NAME   ENABLED     STATE   NEXT_RUN_DATE
----------------------------------------------------------------------------------------------------
DBA_USER MOVE_LISTENER_LOG TRUE       SCHEDULED     25-JUL-11 09.14.59.800000 AM -08:00