[cisco-voip] DB replication not-synch !!!

[Ryan Ratliff]

Try 'utils dbreplication repair'.  That should always be the first  
step in trying to fix dbreplication.

However if only the dynamic tables are showing out of sync that may  
not really be a problem.

-Ryan

On Dec 10, 2008, at 10:25 AM, Djokic Sinisa wrote:

ryan..i see you online - J..



maybe you or wes have an advice?..





thanx..





regards..



Sinisa Djokic

System Engineer
CCNP,CCDA,CQS-CWLDS,CS-CIPTDS,CS-CIPCCES Cisco Certified



<image002.gif>



MDS Informaticki inzenjering
Bul. Arsenija Carnojevica 170
11070 Novi Beograd, Serbia
Tel: +381 11 2015 200, 2015 273
Fax: +381 11 3194 954
www.mds.rs
sdjokic at mds.rs



From: Djokic Sinisa [mailto:sdjokic at mds.rs]
Sent: Wednesday, December 10, 2008 2:52 PM
To: 'cisco-voip at puck.nether.net'
Subject: DB replication not-synch !!!





hi group..

we have a CUCM 6.1.2 cluster with 3 x 7835 and over 1000 phones..

all the phones are registered to subscriber number 1, first backup is  
subsciber number 2, and second backup is publisher..





everything is working fine, but we had some issues with call pickup  
( which we solved by restarting CCM-PUB CCM Sevrvice ) and after that  
we started to monitor system..

during troubleshooting we got to DBREPLICATION..



replication status is 2 and replication count is 393 which seems good..



but when issuing " utils dbreplication status " command among most of  
the log which shows no mismatch or any errors we found these few  
lines which indicate a possible problem in replication ( it's  
regarding mismatch between voip-pub and voip-sub2, there isn't any  
other errors ) :



"



Processing ccmdbtemplate_voip_pub_ccm6_1_2_1000_13_1_343_dnddynamic  
with 1125 rows group 7

------   Statistics for  
ccmdbtemplate_voip_pub_ccm6_1_2_1000_13_1_343_dnddynamic ------

data mismatch between <g_voip_pub_ccm6_1_2_1000_13> and  
<g_voip_sub2_ccm6_1_2_1000_13>

pkid:"245f843a-8821-4cee-aa36-5b9f72e25bdc "

--------------------------------------------------

data mismatch between <g_voip_pub_ccm6_1_2_1000_13> and  
<g_voip_sub2_ccm6_1_2_1000_13>

pkid:"301a7b5e-4a77-4660-8d0b-f8e5c840dddd "

--------------------------------------------------

data mismatch between <g_voip_pub_ccm6_1_2_1000_13> and  
<g_voip_sub2_ccm6_1_2_1000_13>

pkid:"6e39e9c0-d93b-4c8d-8ae0-451b69958dff "

--------------------------------------------------

data mismatch between <g_voip_pub_ccm6_1_2_1000_13> and  
<g_voip_sub2_ccm6_1_2_1000_13>

pkid:"81d3974d-b64f-4019-8203-437690ec8b09 "

--------------------------------------------------

data mismatch between <g_voip_pub_ccm6_1_2_1000_13> and  
<g_voip_sub2_ccm6_1_2_1000_13>

pkid:"97182d31-df7d-4708-be6a-1a0e93c07c24 "

--------------------------------------------------

data mismatch between <g_voip_pub_ccm6_1_2_1000_13> and  
<g_voip_sub2_ccm6_1_2_1000_13>

pkid:"b7ab2a2a-d746-4f30-b945-e46af4193eab "



"



so, does anybody have any opinion, is this out-of-synch between  
publisher and second subscriber something we should be worried about  
or not..



if it needs a fix, what procedure should be the most suitable  
( resetting replication on critical subscriber or on all nodes ):





1.

utils dbreplication stop on  critical subscriber ( second subscriber )
utils dbreplication stop on publisher
utils dbreplication reset <second subsciber> on publisher

restart subscriber afterwards



2.

utils dbreplication stop on  all subscribers
utils dbreplication stop on publisher
utils dbreplication reset all on publisher

restart subscribers afterwards









3. if this  this fails run clusterreset command according to  
procedure 1. or 2.







thanx..





regards..





Sinisa Djokic

System Engineer
CCNP,CCDA,CQS-CWLDS,CS-CIPTDS,CS-CIPCCES Cisco Certified



<image003.gif>



MDS Informaticki inzenjering
Bul. Arsenija Carnojevica 170
11070 Novi Beograd, Serbia
Tel: +381 11 2015 200, 2015 273
Fax: +381 11 3194 954
www.mds.rs
sdjokic at mds.rs



<image002.gif><image003.gif>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081210/ba3ff1ce/attachment-0001.html>