My Oracle Support Banner

Wrong Output From DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING if Calendaring Syntax Contains PERIODS (Doc ID 2233369.1)

Last updated on FEBRUARY 23, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
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.


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.


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.