Stored Function ASAP.CONVERT_GMT_TO_LOCALDB not Properly Converting GMT to Local Time During DST - Daylight Savings Time

(Doc ID 2322306.1)

Last updated on OCTOBER 28, 2017

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Goal

QUESTION

Why is stored function CONVERT_GMT_TO_LOCALDB not properly converting GMT to Local Time during Daylight Savings Time (DST) ?

It seems it is using an old definition for Summer Time.

Please correctly handle each different daylight savings time period:

https://en.wikipedia.org/wiki/History_of_time_in_the_United_States

Start and end dates:

https://en.wikipedia.org/wiki/History_of_time_in_the_United_States#Start_and_end_dates_of_United_States_Daylight_Time

before 2007:

https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_United_States#1975.E2.80.931986:_Extension_of_daylight_saving_time

After 2007:

https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_United_States#2005.E2.80.932009:_Second_extension

 

Maybe it is a relic that time forgot, but it is not Customer code.

Per documentation and SR search:

  1. https://support.oracle.com/epmos/faces/BugDisplay?_afrLoop=588292521107946&id=6178879&_afrWindowMode=0&_adf.ctrl-state=15iqea78lw_97
  2. https://docs.oracle.com/cd/E41106_01/doc.621/e41391/opr_using_op_rpts.htm#BEGIN

 

Solution

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