Some SMS Processes Require Manual Restart After the SMF Database is Shutdown or Fatal Error Occurs
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
The following Network Charging and Control (NCC) daemon processes, running on the Service Managment System (SMS) server, do not detect SMF database shutdown, failover, or fatal errors.
After the SMF database automatically recovers, switches to a failover instance, or is restarted, then these daemons (if running) do not reconnect to the new SMF database instance and will instead constantly generate the following error messages in the SMS server's syslog (/var/adm/messages):
Waht can be done to resolve this issue?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms