THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
|Affected OS Type
||Affected Release Number
11.5(1)SU3b, 11.5(1)SU3a, 11.5(1)SU3
||Slow GUI/Tomcat Response due to Informix Database Issue not being able to run Auto Update Statistics|
Cisco Unified Communications Manager (UCM), Cisco Unity Connection (CUC), or Cisco Unified Communications Manager IM & Presence Service can exhibit slow GUI performance and slow database access due to database query optimizer failure.
Customers can experience slow performance with various database queries. This slowness can be caused by a failure in the automated process that collects the statistics that are used to optimize queries. Most database queries will not be impacted significantly. However, as more of the system data changes over time, the statistics that the optimizer uses can become stale and database queries can become slower.
Administrators can experience slow server performance or operation timeouts when they perform GUI-based queries.
Examples (not exhaustive):
Note: Some functions of the system require database queries as part of the operation.
Cisco customers that run UCM Version 11.5(1)SU4 are not impacted by this defect. For all other customers with impacted releases, Cisco recommends that you upgrade to UCM Version 11.5(1)SU5 or later.
Note: UCM GUI performance issues can have multiple causes. Consult the Troubleshooting Guide for Cisco Unified Communications Manager, Release 11.5(1) and consider these other options:
- Ensure that the VMware OVA file has the proper resources for the configured users and devices.
- Ensure that the virtual disk meets the required performance specifications.
- Ensure that network delays are within specifications and that network issues are resolved.
How To Identify Affected Products
Customers who experience GUI slowness as mentioned in the Problem Symptom section can identify the issue with this command:
file get activelog cm/log/informix/ccm.log
Upon review of the log file, customers will see text similar to this example which identifies the issue:
23:13:59 SCHAPI: last statement aus_refresh_stats(integer,integer)
23:13:59 SCHAPI: [Auto Update Statistics Refresh 43-2] Error -217 Column (aus_cmd_dbs_priority) not found in any table in the query (or SLV is undefined).
See How to Collect CUCM Logs if RTMT isn't Accessible or Available for information on how to collect log files via the CLI.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Cisco Notification Service—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.