My Oracle Support Banner

Scheduled Jobs Failed Because Of Transition To Daylight Saving Time (DST) (Doc ID 2535734.1)

Last updated on MARCH 26, 2021

Applies to:

Oracle Customer Data Management Cloud Service - Version 11.13.18.10.0 and later
Oracle Fusion Financials Common Module Cloud Service - Version 11.13.19.07.0 to 11.13.19.07.0 [Release 1.0]
Information in this document applies to any platform.

Goal

Scheduled Jobs failed because of Transition to Daylight Saving Time (DST)

The Daylight Saving Time (DST) Started on 3/10/2019, it resulted in scheduled import jobs to fail.
There were scheduled jobs, in CDM, following GMT timings.
The desire is to schedule the jobs in DST timings, or in timezone that would not affect the already scheduled processes.
In this specific case, the data was imported from third party source, following the PST timings, as the PST time moved forward by 1 hour, and the CSV files used were uploaded in the third party system, in PST schedule,  the imports were not done, as the files were not available at the time when the process started, because the process started in a timezone that was not updated to the DST time change.

If instead of changing the schedule jobs timings manually every time, to adjust to the DST change, is there any other alternative that could be followed?


Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.