alberto@Ubuntu-Salon:~$ ssh [email protected]@172.16.8.10's
password: Command Line Interface is starting up, please wait ...
Welcome to the Platform Command Line InterfaceVMware
Installation:64 vCPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHzDisk
1: 80GB2048 Mbytes RAMadmin:utils dbreplication clusterreset
********************************************************************************************This
command will repair replication on all nodes in the clusterBefore
running, execute dbreplication stop on all subscribersthen execute
dbreplication stop on the publisherAfter clusterreset, "utils
dbreplication reset all" should be executedfollowed by the reboot
of all
subscribers********************************************************************************************
This command can take considerable amount of time, and will tear
down replication 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
progress admin:utils dbreplication
dropadmindb********************************************************************************************This
command will drop the syscdr database on the serverThis 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
runningCommanded Out of ServiceA Cisco DB
Replicator[NOTRUNNING]Service Manager is runningA Cisco DB
Replicator[STARTED]Dropping of syscdr Database successful.To view
log, use command file view activelog
cm/trace/dbl/sdi/DropAdminDB_20150709_171442.logadmin: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 publisher.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 wideIOWAIT 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 publisher.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 wideIOWAIT 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 and monitor
the progress.Please use 'file view activelog
cm/trace/dbl/sdi/forcedatasyncsub_20150709171633.out' command to
see output admin:utils sysadmin:utils system utils system boot*
utils system restart utils system shutdown utils system
switch-version utils system
upgrade*##########################################################################################################################################################################################3Hi,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_passwordadmin:utils dbadmin: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
stopadmin:utils dbreplication st utils dbreplication status utils
dbreplication stopadmin:utils dbreplication statadmin:utils
dbreplication
status****************************************************************************************************This
command reads and writes database information from all machines and
will take quite some time...please be
patient.****************************************************************************************************--------------------
utils dbreplication status --------------------Output is in file
cm/trace/dbl/sdi/ReplicationStatus.2013_07_02_11_05_56.outPlease
use "file view activelog
cm/trace/dbl/sdi/ReplicationStatus.2013_07_02_11_05_56.out "
command to see the outputadmin:file view activelog
cm/trace/dbl/sdi/ReplicationStatus.2013_07_02_11_05_56.outconnect
to cucmsub1_ccm7_0_2_10000_18 failedEnterprise 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 outputTo 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 tableconnect to
syscdr@cucmsub1_ccm7_0_2_10000_18 failedEnterprise 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################################################################################################################################################################################################################
