How do you tell if 'utils dbreplication reset all' completed successfully?
I had 220.127.116.1100-26 of CUCM installed and upgraded to an Unrestricted version of 18.104.22.16800-5. I later researched that I do not want an Unrestricted version and should have the Restricted instead. I switched versions back to 10000-26 and it warned me I needed to do a 'utils dbreplication reset all' after the Publisher came back up. Note: The Subscriber was never switched over to 13900-5 and remains on the Inactive partition. We only have the two servers, 1 Pub and 1 Sub.
So how do I tell if this dbreplication reset has completed successfully? I've issued the following commands and I will paste the output...
admin:utils dbreplication status
-------------------- utils dbreplication status --------------------
Replication status check is now running in background. Use command 'utils dbreplication runtimestate' to check its progress
The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2012_01_27_22_50_57.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationStatus.2012_01_27_22_50_57.out " command to see the output admin:
admin:utils dbreplication runtimestate
DB and Replication Services: ALL RUNNING
Cluster Replication State: Replication status command started at: 2012-01-27-22-50 Replication status command COMPLETED 530 tables checked out of 530 No Errors or Mismatches found.
Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2012_01_27_22_50_57.out' to see the details
DB Version: ccm8_5_1_10000_26 Number of replicated tables: 530
Do I have to dig through the output file to determine success, or can anyone tell me from the command outputs I've pasted above if it was a success? Once I determine it's successful, I will try and upgrade to the Restricted version of 13900-5.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...