Date Issue While Loading Event Logfile Using UEL After DST Change
(Doc ID 1376438.1)
Last updated on SEPTEMBER 19, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Facing an issue while loading data using UEL.Observed the UEL is adding 1 hour to the input date while constructing the input flist for rating the event. JDK version - 1.5.0_06.
Below is the scenario.
Executed the UEL for below input data:
Below is the input flist constructed by UEL for loading the data via custom opcode:
0 PIN_FLD_POID POID  0.0.0.1 /event/activity/content/tcon/usage -1 0
0 PIN_FLD_QUANTITY DECIMAL  -1
0 PIN_FLD_AMOUNT DECIMAL  1
0 TDB_FLD_EXT_VALUE STR  "-1"
0 PIN_FLD_AUTHORIZATION_ID STR  "TSDP014117823112"
0 PIN_FLD_END_T TSTAMP  (1317789684) Wed Oct 05 15:41:24 2011
0 PIN_FLD_START_T TSTAMP  (1317789680) Wed Oct 05 15:41:20 2011
The input CDR file contains the input date as '20111005121010'. The input flist constructed by UEL has the START_T as '20111005131010', which is not correct. Here there is a difference of 1 hour between CDR input date and input flist's start date. It looks like this issues are happening after the Day light saving time change.
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