How to Manually Force a Full Resync from the SMS to a Replication Node (Doc ID 1262967.1)

Last updated on SEPTEMBER 23, 2022

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 to 4.3.0 [Release 2.2 to 4.3]
Information in this document applies to any platform.

Goal

This Document explains how to run a "Full Resync" to resynchronize <SID>/<SID> DB on Service Logic Controller/Voucher and Wallet Server (also known as UBE) nodes with primary <SID> DB on SMS node.

Solution

	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

1 Login to the machine

2 Edit updateLoaderStartup.sh

3 Restart the updateLoader

3.1 Find the Process ID (PID)

3.2 Kill the process

3.3 Check the process

4 Verify that the resync successfully completes

4.1 Check the log

4.2 Database check

5 Restore previous updateLoader configuration

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.