Wrong Output From DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING if Calendaring Syntax Contains PERIODS
Last updated on FEBRUARY 13, 2017
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Information in this document applies to any platform.
Period keyword can be used as an alternative to interval to indicate a different behavior related to bysetpos.
The EVALUATE_CALENDAR_STRING procedure from the DBMS_SCHEDULER package returns run timestamps by evaluating a specified calendar string. ie, it tells you what the execution dates of a job using the specified calendar string.
While evaluating the calendar string using PERIODs its noticed that it returns the right results for the first 50 dates and then it start skipping.
The output changes after 25th Jan and then again from 16th Feb.
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