Seeder Errors On Intervals Ending 2AM And 3AM On DST Start Day (5-min Intervals) (Doc ID 2898350.1)

Last updated on OCTOBER 06, 2023

Applies to:

Symptoms

Seeder errors on intervals ending 2AM and 3AM on DST start day (5-min intervals)

When attempting to upload 5-min interval data on DST start dates, getting seeder error when trying to upload the interval ending at 2AM or 3AM.

The datetime passed in the CSV upload is the “time ending”.

You would assume that the interval ending at 2AM or 3AM should be processed without error, but both are getting seeder errors with the following error:
Error from Date/Time Shifter is not caused by duplicate hour. (11801, 10910)

This has been observed generally on Measuring Component types built on interval size 00:05:00 with the measuring component BO D1-IntervalChannel. This has been attempted on several measuring component types with the same resulting seeder error. Screenshots have been attached.

Also, you observed this during our attempts to manually alter data via CSV during the 3/14/21 DST start day, but the testing in the screenshots are all for 3/13/22 DST from testing on next year’s DST start day.

You are unable to manually upload data for that 5-minute interval.

ERROR
-----------------------
Error from Date/Time Shifter is not caused by duplicate hour. (11801, 10910)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Go to target Measuring Component
Choose Information/Measuring Component Context Menu Drop-down
Select Load IMDs (CSV)
Choose Choose File on the pop-up dialog and select the file to upload
Check Process Immediately and click Save

Changes

Cause

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