Scheduler Jobs Run Twice at 999th Millisecond
Last updated on NOVEMBER 28, 2017
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms