DAP2 Feature Node Incorrectly Converting Date Format (Doc ID 2930691.1)

Last updated on MARCH 03, 2023

Applies to:

Oracle Communications Network Charging and Control - Version 12.0.4.0.0 and later
Information in this document applies to any platform.

On Oracle Communications Network Charging and Control (OCNCC / NCC) 12.0.4 version, DAP2 feature node is not converting correctly the Date.

Example:
Name: Date1
block=17 tagCode: 3146497
Converted date : 2023-02-27 12:50:03 CET (1677498603)
00 00 00 00 63 FC 98 EB

In slee_acs logs we can see that Date1 has been converted incorrectly by DAP2-309 feature node:

	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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.