SMS Replication failure not reported in SMSMaster/updateLoader log files or syslog (Doc ID 1183523.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Communications Network Charging and Control - Version: 2.4.0 and later   [Release: 2.4 and later ]
Information in this document applies to any platform.


Changes made on the Service Mangement Server (SMS) are not replicated to one or more replication nodes in a timely fashion.

Full resyncs do not work. UpdateLoaders on the Service Logic Controller (SLC) started with -resync will appear to connect to the SMS and do nothing. There are no messages to indicate that replication has started a resync.

Note that this may also occur on the Voucher and Wallet Server (VWS)

/IN/service_packages/SMS/tmp/smsMaster.log on the SMS shows resyncs starting and normal update messages very close together:
Aug 19 21:44:11.680250 smsMaster(3081) NOTICE: FULL Resynchronisation started for node 301
Aug 19 21:44:11.899256 smsMaster(19868) NOTICE: Starting to process normal updates for node 301.


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