Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
After Cisco CallManager 4.1 is upgraded to Cisco CallManager 4.2, CMR files are not inserted into the CDR database, which results in high CPU usage on the server
The call management record (CMR) flat files are not inserted into SQL DB.
Verified in the Publisher SQL Database, there is no varVQMetrics column in the CallDetailRecordDiagnostic table.
Due to missing field in calldetailrecorddiagnostics table, you get Invalid column name errors in detailed trace files, for example:
12/11/2006 12:22:23.899 CDR|Error executing "insert into CallDetailRecordDiagnostic Invalid column name 'varVQMetrics'.|
All CMR files are dropped into the BAD folder by the call detail record (CDR) insert.
Check the C:\Program Files\Cisco\CallDetail\BAD folder if there are many CDR/CMR files there as a result of this problem.
When you check the DBInstall00000000.txt log file, you find the SQL ALTER TABLE statement that should have added the varVQMetrics column, but that failed with the Error on CDR Migrate statement with no other clues.
Also, it is observed each 15-20 minutes that CPU goes to 100% utilization.
The issue is addressed in Cisco bug ID CSCse68968.
A workaround for this bug is:
Stop the insertCDR Service.
Through Enterprise manager or Query analyzer, execute this on the CDR database:
ALTER TABLE CallDetailRecordDiagnostic ADD varVQMetrics varchar(600) DEFAULT NULL NULL
In the CDR file location, move CMR_xxxxxxx files in the BAD folder to the CMRfolder.
Restart CDR Insert service.
Note: You possibly want to move the files from BAD to CMR during off business hours as a precautionary measure.
Use the TAC Service Request Tool in order to open a service request with Cisco Technical Support in order to verify if the fix is released yet in any Service release.