Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 to 5.0.1 [Release 4.4 to 5.0]
Information in this document applies to any platform.
On OCNCC 5.0.1, When the smsMaster process crashes, the replication does not recover as it should be.
The issue can be confirmed by two symptoms :
Symptom 1 : Some node are supposed to be resync'ed as it is noted in the smsMaster.log file :
Symptom 2: As a second symptom, replication update requests made to the Master Replication node by the impacted Replication Update Requester are piling up, blocked on the Master node and causing the rep_ora_renumber table count to constantly increase.
Note that the Master Replication node is the Service Management Server (SMS)
Note that the Replication Update Requester is the Service Logic Controller (SLC) or the Voucher and Wallet Server (VWS)
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