NP NDST Feature Node Hangs slee_acs Resulting in a watchdog SIGABRT
(Doc ID 2654668.1)
Last updated on APRIL 16, 2020
Applies to:Oracle Communications Network Charging and Control - Version 5.0.3 to 220.127.116.11.0 [Release 5.0 to 12.0.0]
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 18.104.22.168.0 [Release 6.0 to 12.0.0]
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), it is possible for the watchdog to abort and restart the slee_acs processes due to unresponsiveness.
A backtrace was not captured at the time of investigation, but from the debug, it can be seen that it last logged line was from the Number Portability (NP) code:
2019/08/27 11:32:47 npDSNodeProcessing.cc 348  npMacroNodes The URI destination parameters are:
2019/08/27 11:32:47 npDSNodeProcessing.cc 348  npMacroNodes URIDestinationBlock: 0
2019/08/27 11:32:47 npDSNodeProcessing.cc 348  npMacroNodes URIDestinationTag: 0x0
2019/08/27 11:32:47 npDSNodeProcessing.cc 355  npMacroNodes acsMacroNpDSProcessing : calledNumber/aec_service_num:<MSISDN>
2019/08/27 11:32:47 npDSNodeProcessing.cc 106  npMacroNodes acsMacroNpDSProcessing : DalGetDNRangeSubOPer
2019/08/27 11:33:36 cmnConfigStreamImpl.cc 38  ConfigFileImpl Constructing an empty cmn::cfg::impl::StreamImpl.
Further testing shows this issue occurs when a lookup is performed by the NP Destination Selection (NDST) for a number that is not provisioned in the NP number ranges.
When the same lookup is performed against a number that is provisioned, the node returns significantly faster.
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