Replication: Check status and fix replication errors

(Difference between revisions)

Revision as of 14:59, 13 June 2012

Problem Summary	Replication is not functioning correctly on one or more Finesse nodes. Database tables are not replicated.
Error Message	None.
Possible Cause	Replication is broken.
Recommended Action	Run the CLI command "utils dbreplication status" from the primary Finesse server. Run the CLI command "utils dbreplication runtimestate". If the RTMT counter value for replication status is 2 on all nodes in the cluster, replication is functioning properly. If the RTMT counter value is 2 or 3 for all nodes in the cluster, replication is set up but there are mismatched rows. Run the CLI command "utils dbreplication repair all" from the primary Finesse server. If the RTMT counter value is something other than 2 or 3 for any node of the cluster, you need to reset replication for that node. From the primary Finesse server, run the CLI command "utils dbreplication reset node name", where node name is the node on which you want to reset replication. Restart the Secondary finesse. If the RTMT counter value is 0 or 1 for the majority of nodes in the cluster, you need to reset replication on the whole cluster. Run the CLI command "utils dbreplication reset all" from the primary Finesse server. Restart the secondary Finesse server.
Release	Release 8.5(3), Release 9.0(1)
Associated CDETS #	None

Rating: 0.0/5 (0 votes cast)

@@ Line 22: / Line 22: @@
 |-
 ! '''Release'''
-| Release 8.5(3)
+| Release 8.5(3), Release 9.0(1)
 |-
 ! '''Associated CDETS #'''
-| None.
+| None
 |}
 <br>
 [[Category:Cisco_Finesse,_Release_8.5]]
+[[Category:Cisco Finesse, Release 9.0]]