cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
431
Views
0
Helpful
3
Replies

CDR_log.ldf file grows extremely large

joe.pollere
Level 1
Level 1

Version: 3.3(4)

Problem Details: The CDR_log.ldf file grows extremely large and consumes all

available disk space on my publisher server. Currently there is only 8 meg free

space available. The CDR_log.ldf file is over 5 gig in size. The CDR.mdf file

is 375 meg.

This is causing BARS to fail due to not enough disk space.

What is causing this and how can I correct it and prevent it from happening.

1 Accepted Solution

Accepted Solutions

scott.searle
Level 1
Level 1

I had the same problem several months ago. Please use the following commands.

C:\>osql -E

1> use CDR

2> go

1> backup log CDR with no_log

2> go

1> dbcc shrinkdatabase (CDR)

2> go

*****You will see some DB output**********

1> exit

Please rate this post if it helped in solving you issue.

View solution in original post

3 Replies 3

scott.searle
Level 1
Level 1

I had the same problem several months ago. Please use the following commands.

C:\>osql -E

1> use CDR

2> go

1> backup log CDR with no_log

2> go

1> dbcc shrinkdatabase (CDR)

2> go

*****You will see some DB output**********

1> exit

Please rate this post if it helped in solving you issue.

Incidentally, one further aspect to be aware of, is the CDR Transaction log, if you are shrinking the CDR database, ensure that you also shrink the transaction log.

This is particulary the case when using a 3rd party CDR application which strips the CDR records from the CallManager. The transaction log will also grow exponentially.

electro22
Level 1
Level 1

Hi -

You can also referr to defect ID CSCea55522.

-Jaret