Last updated on JUNE 22, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Pipeline Manager
An user is on BRM 7.5 PS10 in the Central Time Zone. During DST UTC Offset is -500 and After DST UTC Offset is -600. There are 5-6 hours of window in which call start time and end time stored in database differ with time in CDR by 1 hour.
DST Start for 2016 is March 13, 2016 at 2:00 AM
In this case, all the calls in CFT between March 12, 2016 08:00 PM and March 13 00:59:59 AM are recorded in database with +1 hour. Calls made after 01:00 AM are +2 hours ahead. (It adds 1 hour, and due to time between 2:00 AM and 3:00 AM is not possible on DST start day, it moves 1 more hour)
Calls in CDR after March 13, 2016 03:00 AM are recorded in database with correct timings.
Similarly, DST end for 2015 was November 01, 2015 at 02:00 AM
In this case, all the calls in cdr between October 31, 2015 at 09:00 PM and November 01, 2015 02:00 AM are stored in database with -1 hour.
Further observation, UTC offset is being adjusted as per GMT time. For example, when it is March 12, 2016 08:00 PM in local time Manitoba, it is March 13, 2016 02:00 AM in GMT, and hence 1 hour mismatch. After 6 hours, when local time is also past DST, start UTC offset in CDRs is changed, and correct time is stored.
Similarly when it is October 31, 2015 09:00 AM in Central Time Zone, it is November 01, 2015 02:00 AM in GMT and hence 1 hour mismatch.
Workaround: from DST End, using a custom iScript to manually change the GMT offset in CDR between 5 hour problematic window.
For DST Start, however, same technique is not working for calls between March 12, 2016 08:00 PM to 09:00 PM. The reason being, when it is 08:00 PM in local time in GMT, it is 02:00 AM. Since time between 08:00 PM and 09:00 PM is not valid, so on DST start date, it gives wrong result no matter what offset being used between 08:00 PM and 09:00 PM.
How to resolve this issue?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms