03-19-2005 07:19 AM - edited 03-13-2019 08:26 AM
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.
Solved! Go to Solution.
03-19-2005 10:08 AM
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.
03-19-2005 10:08 AM
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.
03-19-2005 01:59 PM
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.
03-22-2005 09:11 AM
Hi -
You can also referr to defect ID CSCea55522.
-Jaret
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide