Element Management System Oracle Database–Major Error—Database (24) - Cisco BTS 10200 Troubleshooting Manual

Chapter 6 Database Troubleshooting
Element Management System Oracle Database–Major Error—Database (24)
The Element Management System Oracle Database–Major Error alarm (major) indicates that a major
error has occurred in an Oracle background process. The probable cause of the ORA- errors report in
alert.log file is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file. Login to EMS system
as oracle user (or su - oracle) to view this file. If more information is needed, contact Cisco TAC for
database support, or query Oracle metalink library at http://metalink.oracle.com. The corrective action
is documented in the $ORACLE_HOME/rdbms/mesg/oraus.msg file. Login to EMS system as oracle
user (or su - oracle) to view this file. If more information is needed, contact Cisco TAC for database
support, or query the Oracle metalink library at http://metalink.oracle.com. The alert.log file is the
global message file for errors issued by all Oracle background processes. The majority of error
conditions may require administrator's investigation and manual correction. Thus the administrator
should manually clear this alarm.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Secure File Transfer Protocol Transfer Failed—Database (25)
The Secure File Transfer Protocol Transfer Failed alarm (major) indicates that a secure file transfer has
failed. The primary cause of the alarm is that the SFTP was unable to connect between active and standby
call agents. To troubleshoot and correct the primary cause of the alarm, verify communication between
primary and secondary call agent (CA). On each CA, ping the other node. The secondary cause of the
alarm is that the system was unable to login to the remote host. To troubleshoot and correct the secondary
cause of the alarm, verify that the SSH keys have been pre-configured for user root on both active and
standby call agents. The ternary cause of the alarm is that a file transfer error has occurred. To
troubleshoot and correct the ternary cause of the alarm, check the Error dataword to see if it gives an
indication of the kind of error that occurred. It could be a file-system error on the remote host, or a
communication failure between the active and standby call agents.
File Write Error—Database (26)
The File Write Error alarm (major) indicates that a file write error has occurred. The primary cause of
the alarm is that a system error has occurred and that the system may be out of file descriptors. To
troubleshoot and correct the primary cause of the alarm, call Cisco TAC technical support.
Note Refer to the
detailed instructions on contacting Cisco TAC and opening a service request.
Failure Setting the Index Table Soft Limit—Database (27)
The Failure Setting the Index Table Soft Limit alarm (major) indicates that a corruption of the IDX
framework for the table has occurred. To troubleshoot and correct the primary cause of the alarm, run
the tiat command to verify that a corruption has occurred. Once the corruption is verified, fix the
corruption.
OL-8723-19
"Obtaining Documentation and Submitting a Service Request" section on page lvi
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
Troubleshooting Database Alarms
for
for
6-37