09-15-2014 10:19 AM - edited 03-17-2019 12:10 AM
Hello
We are running a cluster of 3 servers with Cisco Call Manager version 6
I have noticed that the replication status is 3 on all servers and from the CM Database Status I can see queue of updates are stuck
I have restarted Pub and one Sub but the status is still 3 and queue status is still the same
Is there anything I can do to make it work?
Thank you
09-15-2014 10:42 AM
Hello,
Can you please try below command and in order to fix this issue
utils dbreplication stop on the subscriber and on the publisher. Wait the process finish on the sub and go to the pub
wait for a few minutes for it to finish
utils dbreplication dropadmindb on the publisher
wait for it to finish
utils dbreplication dropadmindb on the subscriber
wait for a few minutes for it to finish
utils dbreplication reset all on the publisher
Br,
Nadeem
09-15-2014 10:47 AM
Thank you,
I will try them tomorrow, but I thought restarting the servers will also reset the replication
Btw, there was a time difference on the servers due to NTP failure and I have just noticed that Pub can not see one of the Subs, the replication status is 0 and
g_cucs01_ccm6_1_2_1000_13 2 Active Connected 0 Sep 15 10:21:37 g_cucs02_ccm6_1_2_1000_13 11 Active Connected 0 Sep 15 10:35:19 g_cucs03_ccm6_1_2_1000_13 19 Active Dropped 92939 Aug 20 07:51:14 g_cucs08_ccm6_1_2_1000_13 18 Active Local 0
09-16-2014 02:31 AM
Dear Nadeem,
Is restarting the servers the same as issuing these commands?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide