Automated Maintenance Jobs are not Executing After a Change in Server Time
(Doc ID 2370753.1)
Last updated on JANUARY 22, 2020
Applies to:Oracle Database - Standard Edition - Version 10.2.0.1 to 220.127.116.11 [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
The AUTO_SPACE_ADVISOR_JOB and GATHER_STATS_JOB stop running after an accidental change in the server time.
SELECT JOB_NAME, LOG_DATE, STATUS, ADDITIONAL_INFO FROM DBA_SCHEDULER_JOB_LOG WHERE job_name IN ('AUTO_SPACE_ADVISOR_JOB','GATHER_STATS_JOB') and LOG_DATE > sysdate-7
JOB_NAME LOG_DATE STATUS ADDITIONAL_INFO
GATHER_STATS_JOB 16-MAR-18 09.35.58.266000 AM +10:00 STOPPED REASON="Stop job called because associated window was closed" <=============
GATHER_STATS_JOB 27-JAN-18 12.06.42.205000 AM +10:00 SUCCEEDED
AUTO_SPACE_ADVISOR_JOB 27-JAN-18 12.00.08.598000 AM +10:00 SUCCEEDED
AUTO_SPACE_ADVISOR_JOB 16-MAR-18 09.35.58.257000 AM +10:00 STOPPED REASON="Stop job called because associated window was closed" <=============
The production database server time changed from 15/01/2018 to 16/03/2018 on 15/01/2018. The server was like for an hour, then time changed back to current time.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document