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
Unified CCX 11
11.5(1), 11.5(1)SU1, 11.0(1)
Unified CCX 11
||Database Mastership Changes After Connection Pool Runs Out of Connections to DataSource|
Unified Contact Center Express (UCCX) database mastership changes after the Cisco Unified CCX Cluster View Daemon service fails to connect to the master Cisco Unified CCX Database service.
UCCX runs out of connections from its connection pool to connect to the master database, so database mastership fails over to the High Availability (HA) node if an HA node exists.
This issue is triggered by the start of the nightly purge process. This process is configured on the UCCX application administration page under Tools > Historical Reporting > Purge Schedule Configuration.
Every time the scheduled purge process is run, two connections from the Cluster View Daemon service to the database are leaked. After roughly 75 days, the Cluster View Daemon service runs out of possible connections to the CCX database. After the Cluster View Daemon service sees that it cannot connect to the database, database mastership changes.
The problem symptoms include:
- The Master UCCX server has its CCX database service on Standby and shows as Out of Service.
- Syslogs and Real-Time Monitoring Tool (RTMT) show HISTORICAL_DB_WRITE_FAILED alerts from the engine since the CCX database is Out of Service.
- If there is an HA server, the HA Standby server shows the CCX database service as the Master service.
- No configuration changes are possible.
A CCX Cluster View Daemon restart closes all connections in the connection pool and allows new connections to be made afterwards.
Off hours, enter utils service restart Cisco Unified CCX Cluster View Daemon on the impacted node. Ensure the correct node is the master afterwards as restarting the Cluster View Daemon service causes mastership failover.
Once the system is recovered, go to the CCX Administration page and choose Tools > Historical Reporting > File Restore in order to restore the data that was written to flat files while the database was down. It is recommended to perform this operation during a maintenance window or during periods of low call volume if the flat files have been created for multiple days in a high call volume environment.
Unified Contact Center Express 11.5(1) SU1 ES03 Software Download
Unified Contact Center Express 11.6(1) ES02 Software Download
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.