- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
10-06-2014 06:33 AM - edited 03-12-2019 10:11 AM
- Setting changes are not reflected correctly
- Voice Messages are not distributed to the user's mailbox
The CUC cluster consists of the Publisher and Subscriber. The Databases within the cluster will be synchronized by the following two types of Database Replications:
- Enterprise Replication (ER)
- Unity Connection Replication (UCR)
CUCM Database Replication Troubleshooting on the Linux Appliance Model
Without the proper ER running, UCR does not work correctly. So the ER state must be normal at all times.
Specifically, the Replication Status that can be verified by Real Time Monitoring Tool (RTMT) must be 2 for both the Publisher and Subscriber, as shown in the above link.The Replication Status of RTMT can also be confirmed by
show perf query class "Number of Replicates Created and State of Replication".
----- Command execution example -----
[[{"fid":"1036606","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"01_1","field_file_image_title_text[und][0][value]":"01_1","field_media_description[und][0][value]":"01_1"},"type":"media","attributes":{}}]]
2-2. Unity Connection Replication (UCR)
Use the show cuc cluster status command to see if UCR is running normally.
If the status of the replications shown below is Connected, it is running normally.
[[{"fid":"1036611","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"show_cuc","field_file_image_title_text[und][0][value]":"show_cuc","field_media_description[und][0][value]":"show_cuc"},"type":"media","attributes":{}}]]
3-1. If the ER Status is "2" but the UCR status is "Dropped"
You may be able to recover the Database by executing utils cuc cluster overwritedb on the Subscriber to overwrite the Database from the Publisher to the Subscriber.
Note)
Overwriting is completed in a little over five minutes in the laboratory environment where the databases are smaller, but it may take about one hour, depending on the environment.
The Subscriber restarts automatically after executing this command.
There will be no effect to the Publisher, but it is recommended to perform this operation in maintenance window or off hours.
----- Command execution example -----
[[{"fid":"1036616","view_mode":"default","fields":{"format":"default","field_file_image_alt_text[und][0][value]":"02","field_file_image_title_text[und][0][value]":"02","field_media_description[und][0][value]":"02"},"type":"media","attributes":{}}]]
3-2. If the ER Status is "2" but the UCR Status is "Disconnected" or UCR is not recovered by 3-1
It is highly possible that the Subscriber's information on thePublisher Database may be corrupt. In many cases, it requires a reinstallation of the Subscriber.
We may be able to recover your data without reinstalling the Subscriber, depending on our investigation of the case. Please contact Cisco TAC as needed.In addition, please reinstall the Subscriber as follows:
- Shutdown the Subscriber.
- Log into Cisco Unity Connection Administration. Go to [System Setting] > [Cluster] and delete the Subscriber information.
- Restart the Publisher.
- Log into Cisco Unity Connection Administration. Go to [System Setting] > [Cluster] and add the Subscriber again.
- Reinstall the Subscriber.
Recovery may be possible with the utils dbreplication clusterreset command.
utils dbreplication clusterreset command procedure
(1) Execute the utils dbreplication stop command on the Subscriber. Upon completion, proceed to the next step.
----- Command execution example -----
(4) Execute the utils dbreplication dropadmindb command on the Publisher. Upon completion, proceed to the next step.
(6) Execute the utils dbreplication reset all command on the Publisher.
- utils dbreplication runtimestate
- file get activelog cm/trace/dbl/*.log
- file get activelog cm/trace/dbl/sdi/dbmon*.txt
- file get activelog cm/log/informix/dbl_repl*.log
- file get activelog cm/log/informix/ccm*.log
- CUCM Database Replication Troubleshooting on Linux Appliance Model
- Cisco Unity Connection Clustering (CUC cluster overview is explained)
Related Information
Original Document: https://supportforums.cisco.com/ja/document/12180166
Author: Shuhei Mentani
Posted on April 21, 2014