16-25
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 10
Synchronize table contents from the uncorrupted EMS site to the corrupted EMS site.
If the
dbadm -C db
command from
returns out-of-sync table(s) like the examples below, follow
the commands in Step
(below) to synchronize the contents of data from the active EMS
database to the corrupted EMS database.
Text similar to the following example is displayed:
Number of tables to be checked: 130
Number of tables checked OK: 127
Number of tables out-of-sync: 3
List of out of sync tables:
OAMP.TABLE_NAME => 22/0
In this example, one table owned by the OAMP is out of sync. Follow the steps below to synchronize
the contents of the tables:
Note
Execute these commands on the corrupted EMS database to synchronize the table.
Truncate the content of the table on the local database, then copy the data from the remote database, as
follows:
a.
Log in as
oracle
, or
su - oracle
:
b.
Enter the following commands:
$ dbadm -A copy -o <owner> -t <table_name>
$ dbadm -A copy -o oamp -t table_name
Step 11
Verify the Oracle crontab file:
a.
Log in as
oracle
, or
su - oracle
:
b.
Verify the Oracle crontab file on the corrupted EMS site. Compare the schedules of jobs with those
on the active EMS site. If any schedule needs to be modified, enter the following command:
$ crontab -e
