Some Replication Node Tables are Fully Synchronized After Generating a New Replication Configuration File that has Not Been Modified
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.
Every time a new replication config file is generated it triggers enhanced resynchronizations (or resyncs) to all inferior replication nodes even though the replication configuration (~smf_oper/etc/replication.config) has not been modified or changed. A random selection of database tables on some inferior nodes may also do unnecessary full resynchronizations (or resyncs). To recognise this issue a new replication configuration file needs to be generated and the smsMaster and updateLoader logs analyzed.
The Service Management System's (SMS) smsMaster.log file will show the following informational message whenever an enhanced resync is triggered for a node:
This is normal and expected behaviour and a result of poor system administration of the platform. The updateLoader's -resync flag must be disabled once a manual synchronization has completed to prevent unnecessary and unwarranted full resyncs from occurring unexpectedly.
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