CDR issues

-
In CDR, it is the most common issue in CDR.
We get errors like below-

"30023: Data is not available for the date range selected.
Data is available only from Dec, 2009 to Jan 2, 2010"

"10021 no matching record"

Customer panics here and opens TAC case to resolve it. Here I will give you some tips and tricks on how to resolve it quick.


First, check if there are any files in the processed folder. Obviously, there won't be any and you would see the following error-
"no file was found to show"
However, you have checked that files are present in CDR repository, in preserve and car folder.

In such a scenario, first get the output of-
run sql select * from car:tbl_system_preferences
CDR_MAX_DATE              09/16/2010   -> this part is most important as it shows that CAR has data till Sep16
                             
Now, pull the CAR scheduler traces and check why CAR was not loading the data after 16th.

Generally there is a bad CDR/CMR file due to which it can not loads the data.
I provide you a snippet of the error you should get in such a scenario-
2010-01-29 00:01:24,157 ERROR [DailyCdrLoad] controller.CtrLoadCDRRecords - processRecords(): NumberFormatException Error while setting UDT object
java.lang.NumberFormatException: For input string: "3,600"
    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
    at java.lang.Integer.parseInt(Integer.java:456)
    at java.lang.Integer.parseInt(Integer.java:497)
    at com.cisco.ccm.car.controller.CtrLoaderUtil.computeCharge(CtrLoaderUtil.java:1146)
    at com.cisco.ccm.car.controller.CtrLoadCDRRecords.processRecords(CtrLoadCDRRecords.java:1334)
    at com.cisco.ccm.car.services.CDRCMRDBLoader.loadFileToDB(CDRCMRDBLoader.java:433)
    at com.cisco.ccm.car.controller.CtrLoadCDRCMRFiles.loadCDRFiles(CtrLoadCDRCMRFiles.java:522)
    at com.cisco.ccm.car.controller.CtrLoadCDRCMRFiles.load(CtrLoadCDRCMRFiles.java:328)
    at com.cisco.ccm.car.controller.CtrLoader.run(CtrLoader.java:1557)
    at com.cisco.ccm.car.services.SchThread.run(SchThread.java:622)

If you are getting the above error message, it definitely calls for this caveat-
It affects all CM releases prior to 7.1.2.

However, in order to apply the workaround, we have to search unprocessed CDR flat files.

You would see the below snippet in CAR scheduler traces-
2010-12-09 13:46:18,275 DEBUG [DailyCdrLoad] services.CDRCMRDBLoader - loadFileToDB(): Incompatible but loadable CDR/CMR File - cdr_StandAloneCluster_02_201011100918_119521
2010-12-09 13:46:21,328 DEBUG [DailyCdrLoad] services.CDRCMRDBLoader - loadFileToDB(): Incompatible but loadable CDR/CMR File - cdr_StandAloneCluster_01_201011100918_358283
2010-12-09 13:46:24,297 DEBUG [DailyCdrLoad] services.CDRCMRDBLoader - loadFileToDB(): Incompatible but loadable CDR/CMR File - cdr_StandAloneCluster_02_201011100919_119522

All the incompatible files, needs to be deleted so that new files can get generated.

In order to collect all such traces, please make sure that you have set them to detailed and collect them from all nodes.
Click on this link to find out how to set traces to detailed.

Other references.

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more