Johnny, Next time, try the following
- On SUB : utils dbreplication stop - On PUB : utils dbreplication stop utils dbreplication clusterreset I've used the clusterreset successfully when repair and reset don't work Mark. From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Johnny Soong Sent: 05 April 2011 19:03 To: krieger.jul...@gmail.com Cc: ccie_voice@onlinestudylist.com Subject: Re: [OSL | CCIE_Voice] callmanager datebasse replication issue with Publisher. i tried to change the extension on the phone. It did change. So i know replication is not working. I had to revert the configuration on the Callmanager to make it work. I don't know if there is a fix. Publisher replication is down. Repair wont work. Reboot didn't help. Reset doesn't do anything in this case. Since the Replic state is different. If both the Sub and Pub Rpl state is other than 2 and they are the same, then repair will work. Reset will work if you have diferrent repl state. I tried that already. ________________________________ Date: Tue, 5 Apr 2011 19:31:14 +0200 Subject: Re: [OSL | CCIE_Voice] callmanager datebasse replication issue with Publisher. From: krieger.jul...@gmail.com<mailto:krieger.jul...@gmail.com> To: johnnyso...@hotmail.com<mailto:johnnyso...@hotmail.com> CC: ccie_voice@onlinestudylist.com<mailto:ccie_voice@onlinestudylist.com> Hi Johnny, Even if the utils dbreplication commands do not show what we are looking for (2), does the replication work? Try to create a new region on the pub and see if it has replicated to the sub. Then try the following command on the sub to see if it worked : run sql select name from region If replication worked, you should see on your sub the newly created region Julien 2011/4/5 Johnny Soong <johnnyso...@hotmail.com<mailto:johnnyso...@hotmail.com>> I ran into an issue with the Publisher. The DB Replication is broken. It is showing 3 in the state status. When i tried to issue the utils dbreplicate status. It said the following:"Status cannot be performed when replication is down on the publisher, or on a cluster with a single active node; aborting replication status check operation". I did the utils dbreplic stop on the sub and then on the pub. Then i did the utils dbreplic reset 10.10.210.10 on the Pub. It didn't help. Replic is still showing 3 on the Pub. Sub is showing 2 which is fine. I can't issue utils dbreplic repair because the pub replic is down. I rebooted both servers. It didn't do any good. Any suggestion? _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com<http://www.ipexpert.com/>
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
