Total System Power Outage - Cisco BTS 10200 Troubleshooting Manual

Hide thumbs Also See for BTS 10200:

Table of Contents

Element Management System Database Recovery from Hot Backup

Total System Power Outage

If the platforms start, take them down first.

Audit the Oracle database.

Check the mysql database.

Clear the data directories on both CallAgent sides and do a fresh download from the EMS.

On all platforms repeat the following steps:

Discrepancies will have to be fixed via CLI commands.

This may take hours to complete and during this time, call processing is lost, that is why it is critical that

there is no common single point of failure in the power feeds.

Element Management System Database Recovery from Hot

This section provides procedures to restore your Oracle EMS database data files from the most current

hot backup and then recover your database from the backup. If additional archive log backup (by

ora_arch_backup.ksh) was done after the hot backup, the additional archive log backup file sets need to

be restored also. All of these backup file sets are assumed to be located on the remote FTP site.

Directory to restore backup files: /opt/oraback.

The following assumptions were made for this procedure:

Daily backup schedule:

Oracle databases on both primary and secondary EMS systems crashed completely at January 10, 2002,

Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x

Enter the following command:

cd <platform>/bin/data; rm *

Restart both sides using the following command:

platform start all

Do a fresh download (extract Oracle data from the EMS and send it to the Call Agent). See the BTS

10200 Command Line Interface Guide.

Check the transaction queue to make sure that data is going from the EMS to the CA.

Enter the command audit db ems to either make sure everything is in sync.

2:00 AM–daily hot backup (by ora_hot_backup.ksh process)

18:00 PM–daily archive log backup (by ora_arch_backup.ksh process)

Disaster Recovery Procedures

Table of Contents