My Oracle Support Banner

DBMS_SCHEDULER - When Hour Is Specified As 00 In Bytime Clause Next Run Date Not Set Properly (Doc ID 2405053.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


When the hour is specified as 00 in BYTIME clause, hour is not picked of the correct format of 'hour_minute_second_list', instead the clause becomes as 'minute_second_list'.

As per Oracle documentation BYTIME clause in frequency_clause of DBMS_SCHEDULER.CREATE_JOB should accept any valid time in 24HR format. This is not happening when the BYTIME value has Minute in it.

Oracle Doc:


Delivered Result: 2017-11-01 10:30 ... 2017-11-10 10:30
Expected Result: 2017-11-02 00:30 ... 2017-11-11 00:30

Using other values for BYTIME, e.g. 013000 works as expected.

The issue is reproduced in and even with patch 22071479 applied on The bug 22071479 says it is fixed in 12.2. 




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.