My Oracle Support Banner

BICS- Since Daylight Saving Time change, DataSync Job Didn't start As Scheduled (Doc ID 2649556.1)

Last updated on MARCH 19, 2020

Applies to:

Oracle Business Intelligence Cloud Service - Version 17.4.5 and later
Information in this document applies to any platform.

Symptoms

On : NA version, Data Loading

ACTUAL BEHAVIOR
---------------
Since Daylight Saving time started, Data Sync loads didn't start as per the scheduled times.


1. DataSync job which is scheduled at 2:30 AM started at 1:30 AM and failed due to some connectivity issue.
2. Job in DBCS to truncate stage tables which is scheduled at 2:15 AM started at 3 AM
3. Job in DBCS to load Data Warehouse tables which is scheduled at 4:30 AM started at 4:30 AM only.

The gap between the scheduled times and actual start times are not consistent between the jobs.
However, Data Sync Job runs fine when manually triggered.

Changes

 Data Sync schedule working fine until Daylight Saving Time change occurred

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


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