DAP Fails to Read Dates from Profile Tags
(Doc ID 2889271.1)
Last updated on MARCH 27, 2023
Applies to:
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 12.0.5.0.0 [Release 6.0 to 12.0.0]Oracle Communications Network Charging and Control - Version 12.0.0.0.0 to 12.0.5.0.0 [Release 12.0.0]
Information in this document applies to any platform.
Symptoms
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to 12.0.6.0 on Linux, Data Access Pack (DAP) is unable to correctly read an epoch timestamp (seconds since 1970/01/01 00:00:00 Greenwich Mean Time (GMT)) from a profile tag.
Instead, it ends up treating it as epoch 0 and ends up sending "19700101T000000":
The value stored in the profile tag (0x62ece59b) is correctly 1659692443d or Friday, August 5, 2022 9:40:43 AM GMT.
No errors are thrown and this issue does not affect Solaris.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |