My Oracle Support Banner

Integer Profile Fields Are Read Incorrectly (Doc ID 2281788.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 6.0.1 to 6.0.1 [Release 6.0]
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 6.0.1 [Release 6.0]
Information in this document applies to any platform.

Symptoms

Integer profile fields are being interpreted as a four-byte hex string within the control plans.
For example an integer value is found by a APTB(Prefix Tree Branching) feature node and written to integer tag 336 which corresponds to a value of 0x0150 in hexadecimal.

Looking at slee-acs log:

Changes

 

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
Changes
Cause
Solution
References


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