Posted by: Mudassir Ali | June 11, 2010

Troubleshooting the replication issues

Troubleshooting the replication issues

Steps to Troubleshoot CUCM Database Replication Problems in 5.x and 6.x

(written by Bill Benninghoff, heavily borrowing from material written by Laurie Dotter and Nancy Balsbaugh)

If installation has proceeded correctly, then the informix cdr service should be running on the publisher and on each sub in the cluster. “Cdr” in this context means “Continuous Data Replication”, not call detail records.

In order to setup replication, scripts run during the install process that do these things:

a. define replication on the pub

b. define the template on the pub and realize it (tells pub what to replicate)

c. define replication for each sub

d. realize the template on each sub

e. synch the data between the pub and subs using “cdr sync” or “cdr check”

It is possible that this process broke down at one of the steps.

If you look at the RTMT replication counter and see that the replication state counter is a 3 or a 4 for a given server that means replication has failed for that server.

Here are some suggested steps to troubleshoot replication.

1. Check the replication status using the following command logged in on the pub as admin:

a. utils db replication status

This will generate an output file. Study the file to see if replication is setup to each server and if the data is in synch among the servers.

For example:

SERVER ID STATE STATUS QUEUE CONNECTION CHANGED

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: