You are on page 1of 4

Checking MySQL server connection:

MySQL Master Servers connection ..............OK


[-W-] MySQL Slave Server connection Fault in.....: PL0 PL1
MySQL Access Servers connection ..............OK
Pl0 PL_2_3
PL1 PL_2_4

CUDB_21 SC_2_2# cudbSystemStatus -R

Execution date: Fri Aug 11 10:35:27 CAT 2017

Checking Replication Channels in the System:


Node | 11 | 21
====================
[-E-] PLDB ___|__M__|__Xu_
[-E-] DSG 1 __|__M__|__Xu_
[-E-] DSG 2 __|__M__|__Xu_
[-E-] DSG 3 __|__M__|__Xu_
[-E-] DSG 4 __|__M__|__Xu_

CUDB_21 SC_2_2# cd /cluster


CUDB_21 SC_2_2# cd nodes
CUDB_21 SC_2_2# ls -lrt
total 60
drwxr-xr-x 3 root root 4096 Aug 30 2014 1
drwxr-xr-x 4 root root 4096 Aug 30 2014 .sw
drwxr-xr-x 4 root root 4096 Aug 30 2014 10
drwxr-xr-x 4 root root 4096 Aug 30 2014 11
drwxr-xr-x 4 root root 4096 Aug 30 2014 12
drwxr-xr-x 4 root root 4096 Aug 30 2014 13
drwxr-xr-x 4 root root 4096 Aug 30 2014 14
drwxr-xr-x 3 root root 4096 Aug 30 2014 2
drwxr-xr-x 4 root root 4096 Aug 30 2014 3
drwxr-xr-x 4 root root 4096 Aug 30 2014 4
drwxr-xr-x 4 root root 4096 Aug 30 2014 5
drwxr-xr-x 4 root root 4096 Aug 30 2014 6
drwxr-xr-x 4 root root 4096 Aug 30 2014 7
drwxr-xr-x 4 root root 4096 Aug 30 2014 8
drwxr-xr-x 4 root root 4096 Aug 30 2014 9
CUDB_21 SC_2_2# cp /cluster/nodes/3/etc/rpm.conf
/cluster/nodes/3/etc/rpm.conf_FULL
CUDB_21 SC_2_2# grep -ia linux /cluster/nodes/3/etc/rpm.conf_FULL >
/cluster/nodes/3/etc/rpm.conf

CUDB_21 SC_2_2# ssh -p 2024 expert@10.202.4.150


expert@10.202.4.150's password:
Welcome to the DMX CLI
expert connected from 10.202.4.149 using ssh on blade_0_0
expert@blade_0_0 08:45:34> show ManagedElement 1 DmxFunctions 1
BladeGroupManagement 1 Group CUDB ShelfSlot Blade 1
ShelfSlot 0-5
Blade 1
operationalState enabled
availabilityStatus noStatus
productNumber "ROJ 208 840/3"
productRevisionState R6A
productName GEP3-HD300
serialNumber "A065094542 "
manufacturingDate 2013-12-23Z
vendorName "Ericsson AB"
changeDate 2014-09-03T08:32:50Z
busType ipmi
firstMacAddress 34:07:fb:ed:2f:2f
consecutiveMacAddresses 12
CUDB_21 SC_2_2# cudbManageStore --PL 0 -o status
/opt/ericsson/cudb/OAM/bin/cudbManageStore: unrecognized option '--PL'
===================================================
cudbManageStore usage
===================================================

Format(1): cudbManageStore --pl|-p


--order|-o <orderName>
[ --location|-l <backupPath> ]
[ --Script-path|-S <sqlPath> ]
[ --no-start-replication | -n ]
[ --no-ldapfe-restart | -x ]

Format(2): cudbManageStore --ds|-d {<dsId>,<dsId>,...}


--order|-o <orderName>
[ --location|-l <backupPath> ]
[ --Script-path|-S <sqlPath> ]
[ --no-start-replication | -n ]
[ --no-ldapfe-restart | -x ]

Format(3): cudbManageStore --all|-a


--order|-o <orderName>
[ --location|-l <backupPath> ]
[ --Script-path|-S <sqlPath> ]
[ --no-start-replication | -n ]

Format(4): cudbManageStore --help|-h

Where:
-p --pl refers to the local PLDB cluster
-d --ds refers to a local DS cluster. Accepted
values are:
1 to 15: Apply order to the
specified DS storage engine, or
all: Apply order all to
storage engines configured in this CUDB node.
-a --all To refers to all the local clusters
(both PLDB and DS)
-o --order refers to some of the allowed commands
in a CUDB storage engine:
backup
initialize
initndb (*)
kickstart (*)
maintenance
ready
refresh
restart
restore
start
status
stop
toggledebug
mgmnoderestart
ndbrestart
mysqldslvrestart (*)
mysqldacsrestart (*)
mysqldch1mstrestart (*)
mysqldch2mstrestart (*)
masterreplicationrestart
-l --location Specifies backup path from where
obtaining the restore.
If not provided the last backup in
default path specified in parameter
BackupDataDir in config.ini file for
that cluster (in section
[ndbd default]) applies to
<backupPath>.

-S --Script-path Explicitly specify a script to be


executed after
the successful execution of the
restore.
If not provided the default script
applies to <sqlPath> (only for PL)

-i --ndbid Ndb node identifier to be restarted to


initial state.

-n --no-start-replication
Replication is not automatically
started after the successful execution of the restore.
Use only with Group Data Restore.

-x --no-ldapfe-restart
Connections to ldapfe are not
recreated.

-h --help Shows command usage and help

NOTE: The --location|-l <backupPath>, --Script-path|-S <sqlPath>


and --no-start-replication | -n options are only valid for restore
order.

(*) Do not change this value without Ericsson personnel support

Examples:
# This command stop PL clusters in this CUDB Node
> cudbManageStore --pl -o stop

# This command force to restart PL and all DS clusters in this CUDB


Node
> cudbManageStore -a --order start

# This command creates a backup for local DS cluster 3


> cudbManageStore --ds 3 -o backup

# This command moves to maintenance mode all local cluster in this


CUDB Node
> cudbManageStore -d all -o maintenance

CUDB_21 SC_2_2# cudbManageStore -a --order start

cudbManageStore stores to process: pl ds1 (in dsgroup1) ds2 (in


dsgroup2) ds3 (in dsgroup3) ds4 (in dsgroup4).

Launching order start to pl in dsgroup 0.


Launching order start to ds1 in dsgroup 1.
Launching order start to ds2 in dsgroup 2.
Launching order start to ds3 in dsgroup 3.
Launching order start to ds4 in dsgroup 4.
Waiting for start order(s) to be completed in CUDB Node 21 for stores
: pl ds1 ds2 ds3 ds4.
start order finished successfully in CUDB Node 21 for store ds1.
start order finished successfully in CUDB Node 21 for store ds3.
start order finished successfully in CUDB Node 21 for store ds2.
start order finished successfully in CUDB Node 21 for store ds4.
start order failed in CUDB Node 21 for store pl.
start order(s) completed in CUDB Node 21 for stores : pl ds1 ds2 ds3
ds4.
Stores where order start was successfully completed: ds1 ds3 ds2 ds4.

cudbManageStore command with order start failed for stores: pl.