A JOB Created With DBMS_SCHEDULER Without Specifying Any Start_date Gets Executed When Enabling it

(Doc ID 2401293.1)

Last updated on MAY 23, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.2.0.1 [Release 11.2 to 12.2]
Information in this document applies to any platform.

Symptoms

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.

 

Cause

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