My Oracle Support Banner

A JOB Created With DBMS_SCHEDULER Without Specifying Any Start_date Gets Executed When Enabling it (Doc ID 2401293.1)

Last updated on JANUARY 05, 2023

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
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.



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.