ccsCDRLoader Fails to Convert Timestamps of First EDR Processed After Startup
(Doc ID 2339414.1)
Last updated on MARCH 22, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 to 18.104.22.168.0 [Release 6.0 to 12.0.0]
Oracle Communications Network Charging and Control - Version 4.3.0 to 22.214.171.124.0 [Release 4.3 to 12.0.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Convergent Charging Controller (OC3C) and Oracle Communications Network Charging and Control (OCNCC or NCC) up to and including 126.96.36.199, the ccsCDRLoader is able to be configured to do timezone conversion on any date/time Event Data Record (EDR) fields.
This is currently achieved by configuring different timezones in the "TZ" environment variable used by the ccsCDRLoader (this can be configured in the ccsCDRLoaderStartupStartup.sh wrapper script) and the eserv.config configuration item "CCS.ccsCDRLoader.FileWriterCDRLoaderPlugin.cdrTimeZone".
The ccsCDRLoader will use the TZ environment variable as the timezone of the date/time fields of the incoming EDR and the cdrTimeZone configuration item as the desired timezone. It will convert the configured date/time fields as necessary.
Currently an issue affects all OC3C and OCNCC releases where the ccsCDRLoader will fail to correctly convert the first EDR. How it fails depends on 3 factors:
- The timezone of the incoming EDR
- The TZ environment variable
- The cdrTimeZone setting
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