![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 543](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550543.webp)
11-15
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 11 Statistics Troubleshooting
Monitoring Statistics Events
Measurement Table Structured Query Language Write Error—Statistics (10)
The Measurement Table Structured Query Language Write Error event serves as a warning that the
measurement table has had a SQL write error. The primary cause of the event is that there is no database
connection, or the connection is faulty. To correct the primary cause of the event, check to see if there
are any other events generated that indicate there is a database problem. The secondary cause of the
event is that the traffic measurement tables are corrupted. To correct the secondary cause of the event,
correct any database-related problems. The ternary cause of the event is that two processors or more are
attempting to access the table at the same time. To correct the ternary cause of the event, check to see if
all of the database-related problems are cleared, and this warning event report still occurs, contact Cisco
TAC for technical support.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
detailed instructions on contacting Cisco TAC and opening a service request.
Measurement Collection Application Programming Interface
Failure—Statistics (11)
The Measurement Collection Application Programming Interface Failure event serves as a warning that
the measurement collection of application programming interface (API) statistics has failed. The
primary cause of the event is that the report is issued when the traffic measurement subsystem on the
call agent or feature server encounters difficulties when it tries to collect measurement values from one
of the processes. To correct the primary cause of the event execute a
status
command for the affected
call agent or feature server. The secondary cause of the event is that the originating process (for CA, FS
or EMS) is not in active state, or is shut down. To correct the secondary cause of the event, check and
see if the status report indicates that the originating process is down, try to bring the process back into
the normal (In Service) state. If you need assistance in restoring a process, contact Cisco TAC. The
ternary cause of the event is that the platform is currently shutting down the originating process. To
correct the ternary cause of the event, check and see if this event report is being issued every collection
period, contact Cisco TAC for assistance.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
detailed instructions on contacting Cisco TAC and opening a service request.
Note
Traffic measurements will not be available for the affected call agent or feature server from the
measurement period in which this event report was issued.
Measurement Handshake Error–Schema Inconsistency—Statistics (12)
The Measurement Handshake Error–Schema Inconsistency alarm (major) indicates that a measurement
handshake error has occurred. To troubleshoot and correct the cause of the Measurement Handshake
Error–Schema Inconsistency alarm, refer to the
“Measurement Handshake Error–Schema
Inconsistency—Statistics (12)” section on page 11-17
.