Guest

Preview Tool

Cisco Bug: CSCsy75745 - After upgrade old CDR folders/files cannot be removed

Last Modified

Aug 03, 2018

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

7.1(1.39141.2)

Description (partial)

Symptom:

Symptom 1: 
After CUCM upgrade, CDR folders like /var/log/active/cm/cdr_repository/*/<YYYYMMDD> cannot be removed.  Old folders as YYYYMMDD can be seen even way passed the 30 days preservation windows.  For example, if today is 3/26/2009, and you upgraded on 2/1/2009, you can still see some old folders in between 20090101 to 20090202.  These folders are obviously older than 2/26/2009 (which is 30 days ago).  And when you check these folders, they can have wrong permission and/or wrong ownership.  Note that the correct ownership and permission for folders in cdr_repository are: 

ccmservice:ccmbase: for folders in /var/log/active/cm/cdr_repository/*  (Recursively)
drwxrwx---: for /var/log/active/cm/cdr_repository/*
drwxrwxr--: for /var/log/active/cm/cdr_repository/<subfolder>/*  (Here <subfolder> is for car, preserve, processed, destination1, destination2, destination3) 

For example, the folders structure should be something like: 
[root@cscohost]# ls -al /var/log/active/cm/cdr_repository/
total 152
drwxrwxr-x  10 ccmservice ccmbase   4096 Mar 27 17:17 .
drwxrwxrwt   7 root       root      4096 Mar 23 13:54 ..
drwxrwx---  34 ccmservice ccmbase   4096 Mar 27 17:17 car
drwxrwx---  34 ccmservice ccmbase   4096 Mar 27 17:17 destination1
drwxrwx---  34 ccmservice ccmbase   4096 Mar 27 17:17 destination2
drwxrwx---  34 ccmservice ccmbase   4096 Mar 27 17:17 destination3
drwxrwx---  34 ccmservice ccmbase   4096 Mar 27 17:17 preserve
drwxrwx---  34 ccmservice ccmbase   4096 Mar 27 17:17 processed
drwxrwx---   2 ccmservice ccmbase   4096 Mar 25 13:04 tmp
drwxrwx---   2 ccmservice ccmbase   4096 Mar 23 14:00 trans
[root@cscohost]# ls -al /var/log/active/cm/cdr_repository/*/
/var/log/active/cm/cdr_repository/car/:
total 548
drwxrwx---  34 ccmservice ccmbase   4096 Mar 27 17:17 .
drwxrwxr-x  10 ccmservice ccmbase   4096 Mar 27 17:17 ..
drwxrwxr--   2 ccmservice ccmbase   4096 Mar 23 14:01 20090226
drwxrwxr--   2 ccmservice ccmbase   4096 Mar 23 14:01 20090227
drwxrwxr--   2 ccmservice ccmbase   4096 Mar 23 14:01 20090228
...
...

Symptom 2: 
After upgrade, the CDR file soft-links in the /var/log/active/cm/cdr_repository/destination<1/2/3> cannot be removed automatically; so if CDRM with external billing server(s) is configured, you can notice duplicated CDR files keep resending to external billing server(s) over and over again for these older files in the un-removable old YYYYMMDD folders.  

Symptom 3: Similarly, after upgrade, the CDR file soft-links in the /var/log/active/cm/cdr_repository/car cannot be removed automatically; so you can notice duplicated records in CAR database from CDR files being loaded over and over.  If default of the 60 days MAX_CDR_AGE is passed, it can cause these duplicated records to be loaded into the part_remainder partitions.  Use the following queries with root access to determine if there are records in the part_remainder partitions in the two billing tables in CAR db: 

select sp.nrows, sf.partition from sysfragments sf, sysmaster:sysptnhdr sp 
WHERE sf.tabid IN (SELECT tabid FROM systables WHERE tabname='tbl_billing_data') 
and sp.partnum = sf.partn AND fragtype=='T' order by partition;

select sp.nrows, sf.partition from sysfragments sf, sysmaster:sysptnhdr sp 
WHERE sf.tabid IN (SELECT tabid FROM systables WHERE tabname='tbl_billing_error') 
and sp.partnum = sf.partn AND fragtype=='T' order by partition;

Conditions:

If the original CUCM version is 5.x / 6.x (i.e. an older release than 6.00.9901-139), and then eventually upgrade to a 7.x version (i.e. a newer release than 7.0.0.49011-90) with changes from CSCsl10550.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.