This document provides installation instructions for Unified CCE 12.6(2) ES25. It also contains a list of Unified CCE issues resolved by this engineering special. Review all installation information before installing the product. Failure to install this engineering special as described can result in inconsistent Unified CCE behavior.
This document contains these sections:
In the Product
Alert Tool, you can set up profiles to receive email notification of new
Field Notices, Product Alerts, or End of Sale information for your selected
products.
The Product
Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.
While scaling up CCE solution to support 48K agents, we have faced some issues in Logger component. These issues have happened mainly due to high in-flow / processing of historical data messages in logger during load. These problems are addressed by introducing architectural changes in hlgr process of Logger component. Therefore, this patch must be installed on both Logger sides while scaling up CCE solution to 48K agents.
“HKEY_LOCAL_MACHINE\SOFTWARE\Cisco
Systems,
Inc.\ICM\<inst>\LoggerB\Logger\CurrentVersion\Configuration\RecoveryKeyLimitPerSecond”.
The update to recovery key limit from 6000 to 11000 comes with a downside though, in case you wish to uninstall ES25 later. For more information on this, please refer to uninstalling section.
Unified
CCE 12.6(2)
This section lists the Unified CCE components on which you can and cannot install this engineering special.
You can install Unified CCE 12.6(2) ES25 on these Unified CCE components:
Do not install this engineering special on the following components:
Both installation as well as uninstallation of ES25 requires downtime of Logger Component.
Please note that uninstallation of ES25 would bring downtime in logger component on the same day of uninstallation. In order to minimize the impact of this downtime, plan to uninstall ES25 near midnight boundary. For more information on this, please refer to uninstalling section.
Bring both sides of Logger services down before installing
ES25.
Bring both sides of Logger services down before un-installing
ES25.
*Important Note* - After successful uninstallation of ES25, the recovery key limit would be reverted back to 6000. This would not allow logger processes (histlogger / recovery / replication / configlogger ) to come active on the same day of uninstallation due to the fact that the starting recovery key (calculated based on recovery key limit) in logger processes would be smaller than the already persisted historical records in logger database. This problem would get fixed on its own post-midnight. Therefore, please plan to uninstall this ES near midnight boundary. This would minimize the overall downtime duration.
Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.
This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:
Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.
This section lists caveats specifically resolved by Unified CCE 12.6(2) ES25.
Caveats in this section are ordered by UNIFIED CCE component, severity, and
then identifier.
Identifier |
Severity |
Component |
Headline |
CSCwi61466 |
3 |
db.logger |
hlgr asserts due to duplicate recovery key for RouteCallVariable and TerminationCallVariable |
Caveats are ordered by severity then defect number.
Defect Number: CSCwi61466
Component: db.logger
Severity: 3
Headline: hlgr asserts due to duplicate recovery key for RouteCallVariable and TerminationCallVariable
Symptom:
06:37:44:828 la-hlgr Trace: SQL Server User Error:
2601, State 0, Severity: 14, Message: Error: SQLSTATE=23000, Native error=2601,
msg='[Microsoft][ODBC Driver 17 for SQL Server][SQL
Server]Cannot insert duplicate key row in object
'dbo.Termination_Call_VariableTmp1' with unique index 'XPKTermination_Call_Variable'.
The duplicate key value is (1.05092e+013).' 06:37:44:828 la-hlgr
Trace: Additional Bcp Connection made, total
connections 10
Conditions: histlogger assert is seen during
state transfer
Workaround: None
Further Problem Description:
You can access current Cisco documentation on the Support pages at the following sites:
To provide comments about this document, send an email message to the following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your comments.
Cisco.com is a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC site.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. You can also resolve technical issues with online technical support and download software packages. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
The Cisco TAC site is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC site to quickly find answers to your questions.
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following site: https://mycase.cloudapps.cisco.com/create/start/
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following sites:
P1 and P2 level problems are defined as follows: