This document provides information that you can use to shrink the Call
Details Record /CDR Analysis and Reporting (CDR/CAR) database due to
Cisco bug IDs
(registered customers only)
(registered customers only)
)—art_log.ldf file grows very large, CAR
records might stop purging. Both the art_log.ldf and cdr_log.ldf file have been
known to grow very large. This causes low disk space and results in slow Cisco
CallManager performance and/or services are affected.
Ensure that you meet these requirements before you attempt this
The information in this document is based on Cisco CallManager
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
Cisco CallManager returns this SQL error message:
Error No. -2147219942 (0x8004061a): CDBLException Dump:
[Unknown SQL driver error. Please send message to Cisco developer for Telephony
The reason for this error is that SQL transaction log files for some
databases grow over 1 GB in size. The SQL transaction log files are the *.ldf
files located in the C:\Program Files\Microsoft SQL Server\MSSQL\Data
directory. The *.mdf files, especially art.mdf and cdr.mdf, might be larger
that 1 GB depending on system configuration. These solutions only target *.ldf
files greater than 1 GB in size.
Note: Ensure that there are no MGCP devices in your network attempting to
register with Cisco CallManager that are not registered. These devices continue
to attempt to register indefinitely and can cause many megabytes in logs to be
Use the solutions in this section to solve the problem.
The most common problem is that the Backup and Restore System (BARS) is
not configured, or is configured but failing. Make sure backups are set on a
regular basis. During backups, BARS truncates the CDR transaction log. Go to
C:\Program Files\Common Files\Cisco\Log\BARS to review the BARS backup
successful or failed log.
If BARS is truncating and the log and failures occur in the logs, go to
Shrink the database via the SQL Enterprise Manager.
Note: This is done on the Publisher.
Select Start > Programs > MS SQL Server >
Choose the Publisher server.
You can either go to the ART database or CDR database, based on
which file is large.
Right-click the database.
Select All Tasks > Shrink database and click
Select the database file CDR and
CDR_log on the new window.
Shrink each of them.
This process takes some time.
If the file is still large or SQL is not able to shrink the
transactional file, use Solution 3.
For SQL 2000 (Cisco CallManager 3.3 and 4.0), complete these steps to
reduce the size of the CDR_log.LDF. This is located at C:\Program
Files\Microsoft SQL Server\MSSQL\Data.
Use these commands at the command prompt:
1>backup log art with no_log
1>dbcc shrinkdatabase (art)
1>backup log cdr with no_log
1>dbcc shrinkdatabase (cdr)
INF: How to Shrink the SQL Server 7.0 Transaction Log
more information on the Microsoft shrinking database.
This section provides three alternate solutions:
You can configure the CAR purge process to purge less than 500,000
records at any one point in time. Refer to
You can manually delete CDRs without the Administrative Reporting
Tool (ART). Refer to
CallManager: Manually Deleting Call Detail Records (CDRs) Without the
Administrative Reporting Tool (ART).
You can restrict the number of CDR records that go into the database:
Select CCMadmin page Select Service > Service Parameters
> Select the according server > Cisco Database Layer Monitor Service >
Max CDR records.
It is recommended that you perform this task after hours. The
reduction in the number of CDR records causes the deletion process, and the CPU
increases. You can start with increments of 50,000 records. Afterwards, cycle
the database layer monitor service.
Issue Resolution with CDR and ART FAQ to view CDR and CAR FAQs.