Scheduler Jobs Run Twice at 999th Millisecond
(Doc ID 2332433.1)
Last updated on SEPTEMBER 04, 2019
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Cloud Machine - 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 Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
For some reason the start date of a repeating scheduler job is in the 999th millisecond of a timestamp, it will schedule itself to run again immediately.
When searching the dba_scheduler_job_run_details can see the job has been run twice:
The job second run time REQ_START_DATE is 2017-09-07 01:00:00.999651, the 999th millisecond.
Changes
None.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |