About this Document

This document provides installation instructions for Unified CCE 12.5(2) ES39. 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:

Sign Up for Email Notification of New Field Notices

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.

About Cisco Unified CCE (and Unified CCE Engineering Specials)

Unified CCE Compatibility and Support Specifications

Unified CCE Version Support

Unified CCE Component Support

This section lists the Unified CCE components on which you can and cannot install this engineering special.

Supported Unified CCE Components

You can install Unified CCE 12.5(2) ES39 on these Unified CCE components:

Unsupported Unified CCE Components

Do not install this engineering special on the following components:

Unified CCE Engineering Special Installation Planning

Installing Unified CCE 12.5(2) ES39

  1. Download the patch and copy the patch to the local server where patch is going to be installed.
  2. Stop all ICM services and applications running on the server.
  3. Run the patch installer exe and follow the instructions.
  4. Reboot the server on successful completion of the patch install.
  5. Start the ICM services.

Uninstall Directions for Unified CCE 12.5(2) ES39

  1. To uninstall this patch, go to Control Panel.
  2. Select "Add or Remove Programs".
  3. Find the installed patch in the list and select "Remove".

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.

Resolved Caveats in this Engineering Special

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.

Resolved Caveats in Unified CCE 12.5(2) ES39

This section lists caveats specifically resolved by Unified CCE 12.5(2) ES39.

Index of Resolved Caveats

Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
Identifier Severity Component Headline
CSCwi55776 3 db.logger ICM 12.5(2). Some indexes on SQL 2017 Ent were not rebuilt successfully by SQL agent job. Hlgr mdmp.
CSCwi93020 3 db.HDS defragidx only defrags 5 tables at a time.

Detailed list of Resolved Caveats in This Engineering Special

Caveats are ordered by severity then defect number.

Defect Number: CSCwi55776

Component: db.logger

Severity: 3

Headline: ICM 12.5(2). Some indexes on SQL 2017 Ent were not rebuilt successfully by SQL agent job. Hlgr mdmp.

ET is found to resolved the customer issue and same is applicable to main branch (15.0) ES is to be released to customer.
Symptom: Issue we are seeing is that online SQL Index rebuild doesn?t reduce fragmentation for page count greater than 10K and the average fragmentation above 30%. We have an automated SQL job to reduce Index fragmentation using the online option. However, index fragmentation percentage remains high after the job running. The indexes seem not to be rebuilt successfully even that the rebuild operation has been completed without any error.

Conditions: SQL job is programmed to do an Index Rebuild operation (in online mode), installed alongside a SQL Server Enterprise Edition server. If the page count is greater than 10K and the average fragmentation is above 30%, SQL job will attempt to run this online index rebuild. This SQL job is run on a daily basis. Issue we are seeing is online rebuild doesn?t reduce fragmentation.

Workaround: A change is proposed in stored procedure definition, to allow the average fragmentation of indexes to be reduced using the MAXDOP parameter. This would be applicable to only those CCE servers that employ the Enterprise edition of SQL Server. (ET Request) The current implementation where we don?t specify MAXDOP, causes parallel index operations by utilizing as many worker threads as CPUs on the system, and causes the fragmentation at hand. To suppress parallel plan generation, set max degree of parallelism (MAXDOP) to 1. We should run this step of the PurgeTCD job multiple time, while the load is running where high index fragmentation is there. Ensure required load is running with high index fragmentaion. Add MAXDOP=1 at query level as below and run this query to see if index fragmentation can be reduced: ALTER INDEX [XAK2Termination_Call_Detail] ON [t_Termination_Call_Detail] REBUILD WITH (MAXDOP=1, ONLINE = ON ( WAIT_AT_LOW_PRIORITY ( MAX_DURATION = 5 MINUTES, ABORT_AFTER_WAIT = BLOCKERS )));

Further Problem Description: As per logs INDEX REBUILD was performed on index XPKRoute_Half_Hour, XPKRouting_Client_Five_Minute, XPKService_Interval, XIE2Service_Interval, XAK2Termination_Call_Detail, XIE3Termination_Call_Detail, XIE4Termination_Call_Detail from 16:40:37 to 16:49:57 on 2023-10-10. From idxreorg.sql, the rebuild was performed on SQL Enterprise edition with below parameter, indicating if an index is being blocked on the lock, wait 5 minutes and after that kill all blockers: REBUILD WITH (ONLINE = ON (WAIT_AT_LOW_PRIORITY ( MAX_DURATION = 5 MINUTES, ABORT_AFTER_WAIT = BLOCKERS 20231010.xlsx shows indexes rebuilt have fragmentation percent larger than 30%: Profiler shows index XPKRouting_Client_Five_Minute, XPKService_Interval, XIE2Service_Interval were rebuilt. As mentioned, customer stopped the profiler. So, it is not complete, it doesn?t affect all the indexes. There is no specific pattern as such we could establish, but this happens only for a few indexes which have a page count greater than 10k, and a depth level of 4 as per the Physical Statistics Report for the set of Index. The rebuild is run again and note the time difference. --before 98.49 % ALTER INDEX [XIE4Termination_Call_Detail] ON [t_Termination_Call_Detail] REBUILD WITH (ONLINE=ON ( WAIT_AT_LOW_PRIORITY ( MAX_DURATION = 5 MINUTES, ABORT_AFTER_WAIT = BLOCKERS ))); --34 seconds to run results: 96.28 % fragmentation --before 96.28% ALTER INDEX [XIE4Termination_Call_Detail] ON [t_Termination_Call_Detail] REBUILD WITH (MAXDOP=1, ONLINE=ON ( WAIT_AT_LOW_PRIORITY ( MAX_DURATION = 5 MINUTES, ABORT_AFTER_WAIT = BLOCKERS ))); --1 minute 49 seconds to run results: 2.30 % fragmentation So, looks like setting MaxDOP to 1 makes a big difference in bringing down fragmentation.

Defect Number: CSCwi93020

Component: db.HDS

Severity: 3

Headline: defragidx only defrags 5 tables at a time.


Symptom: HDS defrag index procedure only defrags 5 tables even though there are more than 5 tables need defrag.

Conditions: UCCE 12.x Looking at the program where it defrags indexes of the table. It first gets a list of tables and indexes with frag over 30% and page over 10000 into temp table #Frag. Next is to defrag the index of all of them. There are 3 while loops. Outer while loop is for retries. The middle is to fetch distinct table in the temp table #Frag. The inner while loop is to go through each index in the table get from middle loop and drage that index. The problem is the middle loop which never fetches the next table. That's why it will only try 5 tables (5 retries) even though you may have more than 5 distinct tables in the #Frag.

Workaround: Complete the middle loop calling @@FetchStatus on next listed table. installer changes is required. It is backported from main(15.0) to 1252.

Further Problem Description: The problem is the middle loop which never fetches the next table. That's why it will only try 5 tables (5 retries) even though you may have more than 5 distinct tables in the #Frag. Fix fetches next table, hence no skip from the loop.

Obtaining Documentation

You can access current Cisco documentation on the Support pages at the following sites:

Documentation Feedback

To provide comments about this document, send an email message to the following address:

contactcenterproducts_docfeedback@cisco.com

We appreciate your comments.

Obtaining Technical Assistance

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

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.

Technical Assistance Center

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.

Contacting TAC by Using the Cisco TAC Site

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/

Contacting TAC by Telephone

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: