Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide

The runTruncateHistDBLogs command can spend up to 5 minutes per database 
log file performing the truncation. If you are substantially truncating a log file, 
this time limit may not allow the command to truncate the log file to the size that 
you specified. In this case, rerun the runTruncateHistDBLogs command to 
truncate the log files to the desired size.

To ensure that the truncated log files are updated with current information, 
perform a complete backup of the CRS databases and log files after executing the 
runTruncateHistDBLogs command.

The syntax for the runTruncateHistDBLogs command is:

runTruncateHistDBLogs {“db_cra” | “tempdb”} size

The table that follows lists the options and parameters for the 
runTruncateHistDBLogs command.

For example, the following command truncates the db_cra_log.ldf database 
transaction log file to 250 MB:

If the database on the CRS server is down, historical records are cached to be 
written to the database. If the number of records exceeds the cache maximum, the 
additional records are written to files stored in the wfaavid\SQLdata directory. 
These data files are also generated if the historical record queue is exceeded when 
the database on the Expansion server and CRS server are down. 

“db_cra”

Truncates the db_cra_log.ldf database transaction log file.

Truncates the tempdb.ldf database transaction log file.

Size in MB to which the file or files will be truncated.

For the ldb_cra_log.ldf file, specify a size value no less than 
one-fourth the size of the ldb_cra.mdf database.