Table Size Exceeds Minor Threshold Limit—Database (14) - Cisco BTS 10200 Troubleshooting Manual

Chapter 6 Database Troubleshooting
Table Size Exceeds Minor Threshold Limit—Database (14)
The Table Size Exceeds Minor Threshold Limit alarm (minor) indicates that the table size has exceeded
the minor threshold crossing limit. The primary cause of the alarm is that the pre-provisioned size for
the stated table is nearing the licensed limit on the number of entries it can hold. To correct the primary
cause of the alarm, contact Cisco TAC to purchase additional entry space for this particular table.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, collect the following information:
show db-usage table_name=<string>
Table Size Exceeds Major Threshold Limit—Database (15)
The Table Size Exceeds Major Threshold Limit alarm (major) indicates that the table size has exceeded
the major threshold crossing limit. The primary cause of the Table Size Exceeds Major Threshold Limit
alarm is the major threshold crossing limit has been exceeded. No further action is required.
Table Size Exceeds Critical Threshold Limit—Database (16)
The Table Size Exceeds Critical Threshold Limit alarm (critical) indicates that the table size has
exceeded the critical threshold crossing limit. The primary cause of the alarm is that the critical threshold
limit was exceeded. No corrective action is required.
Data Replication Failed—Database (17)
The Data Replication Failed alarm (major) indicates that the data replication failed. The primary cause
of the alarm is that an index is out of range. The secondary cause of the alarm is that a record size
mismatch occurred. No corrective action is required.
Replication Data Flush Timeout During Switchover—Database (20)
The Replication Data Flush Timeout During Switchover alarm (major) indicates that the replication data
flush timed out during a switchover. The primary cause of the alarm is that a Replication Module
software problem has occurred. To correct the primary cause of the alarm, a database restore procedure
needs to be executed on the side which goes active after a switchover. The alarm should be cleared
manually after recovery action is taken.
OL-8723-19
"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
6-33