Replication: Check status and fix replication errors

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
m (1 revision)
 
(One intermediate revision not shown)
Line 1: Line 1:
-
== Replication: Check status and fix replication error  ==
+
== Replication: Check RTMT status and fix replication error  ==
{| border="1"
{| border="1"
Line 22: Line 22:
|-
|-
! '''Release'''  
! '''Release'''  
-
| Release 8.5(3), Release 9.0(1)
+
| Release 8.5(3), Release 9.0(1), Release 9.1(1)
|-
|-
! '''Associated CDETS #'''  
! '''Associated CDETS #'''  
Line 28: Line 28:
|}
|}
-
<br>
+
<br>&nbsp;
-
[[Category:Cisco_Finesse,_Release_8.5]]  
+
[[Category:Cisco_Finesse,_Release_8.5]] [[Category:Cisco_Finesse,_Release_9.0]] [[Category:Cisco_Finesse,_Release_9.1]]
-
 
+
-
[[Category:Cisco Finesse, Release 9.0]]
+

Latest revision as of 20:33, 10 January 2013

Replication: Check RTMT status and fix replication error

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
  1. Run the CLI command "utils dbreplication status" from the primary Finesse server.
  2. 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.
  3. 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.
  4. 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.
  5. 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), Release 9.1(1)
Associated CDETS # None


 

Rating: 0.0/5 (0 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Replication:_Check_status_and_fix_replication_errors"
Personal tools