alberto@Ubuntu-Salon:~$ ssh admin@172.16.8.

10
admin@172.16.8.10's password:
Command Line Interface is starting up, please wait ...
Welcome to the Platform Command Line Interface
VMware Installation:
64 vCPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
Disk 1: 80GB
2048 Mbytes RAM

admin:utils dbreplication clusterreset

********************************************************************************
************
This command will repair replication on all nodes in the cluster
Before running, execute dbreplication stop <server> on all subscribers
then execute dbreplication stop on the publisher
After clusterreset, "utils dbreplication reset all" should be executed
followed by the reboot of all subscribers
********************************************************************************
************
This command can take considerable amount of time, and will tear down replicatio
n and build it back again.
Are you sure you want to continue? (y/n):y
Repairing of replication is in progress.
You may tail /cm/trace/dbl/sdi/clusterReset_20150709171343.out to observe progre
ss
admin:utils dbreplication dropadmindb
********************************************************************************
************
This command will drop the syscdr database on the server
This should be executed if replication reset fails
It can be executed on both publisher and subscriber servers
********************************************************************************
************
Dropping the syscdr database is in progress.
Service Manager is running
Commanded Out of Service
A Cisco DB Replicator[NOTRUNNING]
Service Manager is running
A Cisco DB Replicator[STARTED]
Dropping of syscdr Database successful.
To view log, use command file view activelog cm/trace/dbl/sdi/DropAdminDB_201507
09_171442.log
admin:utils dbreplication forcedatasyncsub
********************************************************************************
*********

WARNING !!!
This command will erase existing data on the subscriber.
Root Cause Analysis is not possible after running this command.
This command will force the specified subscriber(s) to take a backup from the pu
blisher.
The subscriber will be restored with the publisher's backup.
This command can only be run on the publisher.
After running make sure to reboot the restored subscriber.
This command can take significantly long time and can also affect the system wid
e
IOWAIT on your system
********************************************************************************
*********
Are you sure you want to continue? (y/n):y
This command may take a significant amount of time. Please be patient.
Usage:
********************************************************************************
********
admin:utils dbreplication forcedatasyncsub nodo2
********************************************************************************
*********
WARNING !!!
This command will erase existing data on the subscriber.
Root Cause Analysis is not possible after running this command.
This command will force the specified subscriber(s) to take a backup from the pu
blisher.
The subscriber will be restored with the publisher's backup.
This command can only be run on the publisher.
After running make sure to reboot the restored subscriber.
This command can take significantly long time and can also affect the system wid
e
IOWAIT on your system
********************************************************************************
*********
Are you sure you want to continue? (y/n):y
This command may take a significant amount of time. Please be patient.
Restore Completed.
Please reboot the subscriber.
You can find the logs at cm/trace/dbl/sdi/forcedatasyncsub_20150709171633.out an

d monitor the progress.

Please use 'file view activelog cm/trace/dbl/sdi/forcedatasyncsub_20150709171633
.out' command to see output
admin:utils
admin:utils
utils
utils
utils
utils
utils

sys
system
system
system
system
system
system

boot*
restart
shutdown
switch-version
upgrade*

################################################################################
################################################################################
##########################3
Hi,
I am using version 7.0.2.10000-18. Out put of utils dbreplicate status:
admin:utils re
utils remote_account
utils reset_ui_administrator_name
utils reset_ui_administrator_password
admin:utils db
admin:utils dbreplication
utils dbreplication clusterreset
utils dbreplication dropadmindb
utils dbreplication forcedatasyncsub
utils dbreplication repair
utils dbreplication reset
utils dbreplication setrepltimeout
utils dbreplication status
utils dbreplication stop
admin:utils dbreplication st
utils dbreplication status
utils dbreplication stop
admin:utils dbreplication stat
admin:utils dbreplication status
********************************************************************************
********************

This command reads and writes database information from all machines and will ta
ke quite some time...please be patient.
********************************************************************************
********************
-------------------- utils dbreplication status -------------------Output is in file cm/trace/dbl/sdi/ReplicationStatus.2013_07_02_11_05_56.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationStatus.2013_07_02_11
_05_56.out " command to see the output
admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2013_07_02_11_05_56
.out
connect to cucmsub1_ccm7_0_2_10000_18 failed
Enterprise Replication not active (62)
command failed -- unable to connect to server specified (5)
------------------------------------------------No Errors or Mismatches found.
Replication status is good on all available servers.
utils dbreplication status output
To determine if replication is suspect, look for the following:
(1) Number of rows in a table do not match on all nodes.
(2) Non-zero values occur in any of the other output columns for a table
connect to syscdr@cucmsub1_ccm7_0_2_10000_18 failed
Enterprise Replication not active (62)
command failed -- unable to connect to server specified (5)
Error Details:
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 20 of 32) :
admin:
Thuc
################################################################################
################################################################################
################################################