Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
A control plan using DAP (Data Access Pack) services is failing with its DAP2 node exiting out its error branch and generating the following critical alarm message:
However, further investigations using debug call tracing showed that this DAP2 node had valid, non null profile fields to access and therefore it was a spurious error. On further investigation it was found that another earlier DAP2 node was trying to access an invalid profile tag, but it was not until the second DAP2 node logic was executed that the critical error was being reported. Fixing the profile field in the first DAP2 node resolved the issue and the DAP service's control plan flow completed as expected.
A bug was raised to investigate why the error message did not correctly occur for the first DAP2 node, and thereby aid in successfully diagnosing the issue earlier.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms