A JOB Created With DBMS_SCHEDULER Without Specifying Any Start_date Gets Executed When Enabling it
Last updated on MAY 23, 2018
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2 to 12.2]
Information in this document applies to any platform.
There is an old job that was in DISABLED status and had no start date, no end date. However, during a weekend activity this job as enabled by mistake by a script, and then the job started.
We thought that not having a START DATE, an END DATE and a FREQUENCY a job would have not been started by oracle even if enabled.
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