/mcpTroubleshoot CUCM Database Replication Issues Contents Introduction Steps to Diagnose the Database Replication Step 1. Verify Database Replication is Broken Step 2. Collect the CM Database Status from the Cisco Unified Reporting Page on CUCM Step 3. Review the Unified CM Database Report of any Component Flagged as an Error Step 4. Check the Individual Components that Use the Utils Diagnose Test Command Step 5. Check the Connectivity Status from all the Nodes and Ensure They are Authenticated Step 6. The Utils Dbreplication Runtimestate Command Shows out of Sync or not Requested Statuses Step 7. Repair All/Selective Tables for Database Replication Step 8. Reset the Database Replication from Scratch Related Information Introduction This document describes how to diagnose database replication issues and provides the steps necessary to troubleshoot and resolve those issues. Steps to Diagnose the Database Replication This section describes scenarios in which database replication is broken and provides the troubleshooting methodology in order to diagnose and isolate the problem. Step 1. Verify Database Replication is Broken In order to determine whether your database replication is broken, you must know the various states of the Real Time Monitoring Tool (RTMT) for the replication. Value Meaning Description 0 Initialization State Replication is in the process of setting up. A setup failure can occur if replication is in this state for more than an hour. 1 The Number of replicates is incorrect Set up is still in progress. This state is rarely seen in versions 6.x and 7.x; in version 5.x, it indicates that the setup is still in progress. 2 Replication is good Logical connections are established and the tables are matched with the other servers on the cluster. Logical connections are established but there is an uncertainty whether the tables match. In versions 6.x and 7.x, all servers could show state 3 even if one server is down in the cluster. This issue can occur because the other servers are unsure whether there is an update to the User Facing Feature (UFF) that has not been passed from the subscriber to the other device in 3 Mismatched tables