Download and deploy the latest qos_processor from:
https://techdocs.broadcom.com/us/product-content/recommended-reading/technical-document-index/ca-unified-infrastructure-management-hotfix-index.html?r=2&r=1Hotfix:
qos_processor-9.1.0-HF1.zipThis hotfix addresses the following:
- DE423431 : This hotfix will contain the fix for checksum value calculation issue from qos_processor.
***Dependencies/Prerequisites***
Apply data_engine-9.2.0-HF4 before applying current patch. Refer to its release notes.
Steps to apply the current patch:
1. Deactivate the qos_processor probe in the UIM server.
2. Import the zip file to local archive
3. Deploy the imported package to primary hub robot system
4. Activate the qos_processor probe in the UIM server
We also had to do the following to prevent any further corrupt checksums:
- Deactivate qos_processor
- Empty the queue a few times
- Run the following sql statement (which may take up to 10 mins) in MS SQL Server Studio
===================================
update qos_dataset checksum = CONVERT(VARCHAR(41),HashBytes('SHA1', convert(varchar(1024),CONCAT(qos_data.qos,'#',qos_data.source,'#',qos_data.target,'#',qos_data.origin))),2)FROM S_QOS_DATA qos_dataINNER JOIN S_QOS_DATA T on qos_data.table_id = T.table_id and T.checksum!=CONVERT(VARCHAR(41),HashBytes('SHA1', convert(varchar(1024),CONCAT(qos_data.qos,'#',qos_data.source,'#',qos_data.target,'#',qos_data.origin))),2);===================================
Via the hub Status Tab, empty the qos_processor message queue again,
- Activate the qos_processor
- Check the qos_processor logs to make sure there are no more entries indicating corrupt checksums.