![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 224](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550224.webp)
6-30
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 6 Database Troubleshooting
Troubleshooting Database Alarms
Element Management System Database Replication DefTranDest Queue
Overloaded—Database (6)
The Element Management System Database Replication DefTranDest Queue Overloaded alarm (major)
indicates that the EMS database replication DefTranDest queue is overloaded. The primary cause of the
alarm is that the replication PUSH job is broken. To correct the primary cause of the alarm, correct the
problems on remote database. The secondary cause of the alarm is that the remote database is not
accessible. To correct the secondary cause of the alarm, verify that the db_heart_beat process is up. The
ternary cause of the alarm is that the database is overloaded. To correct the ternary cause of the alarm,
troubleshoot database performance.
For additional troubleshooting information, execute the following:
On one EMS server:
su - oracle
dbadm -C rep
On both EMS servers:
nodestat
dbadm -r get_deferror
dbadm -r get_deferr
dbadm -r get_deftrandest
dbadm -r get_defcall_order
Note
Do not perform an EM01 switchover until the deferrors are removed.
Element Management System Database DefTran Queue is
Overloaded—Database (7)
The Element Management System Database DefTran Queue is Overloaded alarm (minor) indicates that
the EMS database DefTran queue is overloaded. The primary cause of the alarm is that the replication
DefTranDest queue is overloaded. To correct the primary cause of the alarm, resume replication
activities. The secondary cause of the alarm is that there are too many errors in DefError queue. To
correct the secondary cause of the alarm, correct the replication errors. The ternary cause of the alarm is
the replication PURGE job is broken or overloaded. To correct the ternary cause of the alarm, enable the
replication PURGE job.
For additional troubleshooting information, execute the following:
On one EMS server:
su - oracle
dbadm -C rep
On both EMS servers:
nodestat
dbadm -r get_deferror
dbadm -r get_deferr
dbadm -r get_deftrandest
dbadm -r get_defcall_order
Note
Do not perform an EM01 switchover until the deferrors are removed.