DBMS_SCHEDULER - When Hour Is Specified As 00 In Bytime Clause Next Run Date Not Set Properly
Last updated on JUNE 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 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.
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 22.214.171.124.0 and 126.96.36.199 even with patch 22071479 applied on 188.8.131.52.0. The bug 22071479 says it is fixed in 12.2.
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