16-21
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 16 Disaster Recovery Procedures
Recovering the Element Management System Database from Another Database
Step 6
Stop all transactions except northbound traffic on the active EMS. From the active EMS side, stop all
transactions to the database except northbound traffic and status control update from CA or FS.
Caution
There is no CLI provisioning and Simple Network Management Protocol (SNMP) processes
must be stopped.
a.
Log in as
root
.
b.
Enter the following command:
# pkill smg3
Step 7
Copy data from the active EMS database to the corrupted database:
Caution
During this step the
dbadm -A copy_all
process will truncate local tables first, then copy data
from the tables on the other site.
Make sure that you execute this step on the corrupted EMS
side only.
a.
On the corrupted EMS side, log in as
oracle
, or
su – oracle
.
Note
Make sure that you are on the corrupted database site.
b.
Enter the following command:
$ dbadm -A copy_all
Text similar to the following is displayed:
*****************************************************************
You are about to execute the following process:
==> Copy all OAMP/OPTICALL/BILLING tables from remote DB optical1 at priems47
database: optical2
hostname: secems47
*****************************************************************
c.
At the prompt, enter
y
to continue:
Do you want to continue? [y/n] y
Text similar to the following is displayed:
***This will EMPTY all the tables on:
*** local host ==> secems47
*** local database ==> optical2
***
*** Then copy data from remote DB optical1 at priems47
