DBMS_SCHEDULER - When Hour Is Specified As 00 In Bytime Clause Next Run Date Not Set Properly
(Doc ID 2405053.1)
Last updated on AUGUST 04, 2018
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
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:
https://docs.oracle.com/database/121/ARPLS/d_sched.htm#ARPLS72235
eg:
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 12.1.0.2.0 and 12.2.0.1 even with patch 22071479 applied on 12.1.0.2.0. The bug 22071479 says it is fixed in 12.2.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |