The TBLU Feature Node Writes Corrupted Values to Profile Tags
(Doc ID 2477791.1)
Last updated on MAY 06, 2020
Applies to:
Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.2 [Release 4.3 to 5.0]Information in this document applies to any platform.
Symptoms
On all versions of Oracle Communications Network Charging and Control (OCNCC and NCC) up to 5.0.1 (inclusive), there is a known issue with the Table Lookup (TBLU) Feature Node (FN) where corrupt values are occasionally being stored in the target Profile Tag.
For example, assuming the lookup data has been preloaded so a lookup of "123" returns "456", then instead of "456" being written to the target Profile Tag, a garbled value such as:
is written instead.
This does not affect every lookup and is completely random, even for the same lookup.
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 |