 |
|
 |
|
01-31-07 12:11 PM
Hi,
I have noticed that my CDR_log.LDF file, that is located in C:\Program Files
\Microsoft SQL Server\MSSQL\Data has a size of 32GB and is growing 5GB per w
eek. I suppose there should be a bug behind, but the for the moment I want t
o stop this growing...
Do you know if it is enough with putting the service parameter CDR Enabled f
lag to false to stop collecting CDR information? Later on I'll see how we wi
ll purge this because I assume it will be a CPU intensive process...
I have a TAC case opened, but for the moment the engineer it is not helping
me very much...
Regards,
Ruben
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: CDR_log.LDF huge size |
 |
 |
|
|
01-31-07 12:11 PM
There are a couple of things here. First you need to ensure the records
are being pruned, have you changed the max numbers of records allowed
from the default of 1.2million, DBL service parameter? Is CAR installed
& configured to remove CDR & ART records after a set number of days? If
the answer to all of the above is yes you may have an issues with the
transaction log not being cleared. You cab check the transaction in SQL
Enterprise Manager by changing the view to Status View, it will be in
the left window graphically. Keep in mind that once the total allocated
space is expanded it will never shrink in size by it's self. Also
regular backups of the Pub will truncate & purge automatically.
To purge the transaction log & shrink the DB manually in SQL query
analyzer, may or may not need the "'s depending on the SQL version:
Here is how we truncated the transaction log for CDR:
1) ISQLW
2) select the CDR DB
3) execute "dump tran "CDR" with no_log"
Had to truncate the ART transaction log through ISQLW:
1) ISQLW
2) select the ART DB
3) execute "dump tran "ART" with no_log"
Mike
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Ruben Montes
(Europe)
Sent: Wednesday, January 31, 2007 3:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CDR_log.LDF huge size
Hi,
I have noticed that my CDR_log.LDF file, that is located in C:\Program
Files\Microsoft SQL Server\MSSQL\Data has a size of 32GB and is growing
5GB per week. I suppose there should be a bug behind, but the for the
moment I want to stop this growing...
Do you know if it is enough with putting the service parameter CDR
Enabled flag to false to stop collecting CDR information? Later on I'll
see how we will purge this because I assume it will be a CPU intensive
process...
I have a TAC case opened, but for the moment the engineer it is not
helping me very much...
Regards,
Ruben
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: CDR_log.LDF huge size |
 |
 |
|
|
01-31-07 12:11 PM
Ruben,
You need to truncate the log file. There is a sql command to do it.
Alternatively if you back up with BARS select CDR and BARS will truncate
for you as part of the backup process.
Joe
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Ruben Montes
(Europe)
Sent: Wednesday, January 31, 2007 4:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CDR_log.LDF huge size
Hi,
I have noticed that my CDR_log.LDF file, that is located in C:\Program
Files\Microsoft SQL Server\MSSQL\Data has a size of 32GB and is growing
5GB per week. I suppose there should be a bug behind, but the for the
moment I want to stop thisgrowing...
Do you know if it is enough with putting the service parameter CDR
Enabled flag to false to stop collecting CDR information? Later on I'll
see how we will purge this because I assume itwill be a CPU intensive
process...
I have a TAC caseopened, but for the moment the engineer it is not
helping me very much...
Regards,
Ruben
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: CDR_log.LDF huge size |
 |
 |
|
|
01-31-07 06:11 PM
Hi,
BARS is actually not backing up the CDR. Can I still configure it now or it'
s too late due to the size of the file?
Thanks,
Ruben
________________________________
De: Joe Pollere (US) [mailto:Joe.Pollere@us.didata.com]
Enviado el: mié 31/01/2007 13:59
Para: Ruben Montes (Europe); cisco-voip@puck.nether.net
Asunto: RE: [cisco-voip] CDR_log.LDF huge size
Ruben,
You need to truncate the log file. There is a sql command to do it. Alternat
ively if you back up with BARS select CDR and BARS will truncate for you as
part of the backup process.
Joe
________________________________
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck
.nether.net] On Behalf Of Ruben Montes (Europe)
Sent: Wednesday, January 31, 2007 4:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CDR_log.LDF huge size
Hi,
I have noticed that my CDR_log.LDF file, that is located in C:\Program Files
\Microsoft SQL Server\MSSQL\Data has a size of 32GB and is growing 5GB per w
eek. I suppose there should be a bug behind, but the for the moment I want t
o stop this growing...
Do you know if it is enough with putting the service parameter CDR Enabled f
lag to false to stop collecting CDR information? Later on I'll see how we wi
ll purge this because I assume it will be a CPU intensive process...
I have a TAC case opened, but for the moment the engineer it is not helping
me very much...
Regards,
Ruben
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: CDR_log.LDF huge size |
 |
 |
|
|
01-31-07 06:11 PM
It may take a while but you can still enable BARS to back up your =
CDRs. If your transaction log is filling up that quickly then it =
sounds like you have a pretty hefty call volume and you have hit he =
max amount of CDR records so Aupair is having to delete a lot of them =
to bring you back down. The max records by default is 1.5 million =
and is set via a service parameter for Database Layer Monitor (aka =
Aupair).
There is a SQL job that will truncate the logs as well but it only =
triggers if the c: drive gets below 500Mb free space.
-Ryan
On Jan 31, 2007, at 8:54 AM, Ruben Montes ((Europe)) wrote:
Hi,
BARS is actually not backing up the CDR. Can I still configure it now =
or it's too late due to the size of the file?
Thanks,
Ruben
De: Joe Pollere (US) [mailto:Joe.Pollere@us.didata.com]
Enviado el: mi=E9 31/01/2007 13:59
Para: Ruben Montes (Europe); cisco-voip@puck.nether.net
Asunto: RE: [cisco-voip] CDR_log.LDF huge size
Ruben,
You need to truncate the log file. There is a sql command to do it. =
Alternatively if you back up with BARS select CDR and BARS will =
truncate for you as part of the backup process.
Joe
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip- =
bounces@puck.nether.net] On Behalf Of Ruben Montes (Europe)
Sent: Wednesday, January 31, 2007 4:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CDR_log.LDF huge size
Hi,
I have noticed that my CDR_log.LDF file, that is located in C: =
\Program Files\Microsoft SQL Server\MSSQL\Data has a size of 32GB and =
is growing 5GB per week. I suppose there should be a bug behind, but =
the for the moment I want to stop this growing...
Do you know if it is enough with putting the service parameter CDR =
Enabled flag to false to stop collecting CDR information? Later on =
I'll see how we will purge this because I assume it will be a CPU =
intensive process...
I have a TAC case opened, but for the moment the engineer it is not =
helping me very much...
Regards,
Ruben
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: CDR_log.LDF huge size |
 |
 |
|
|
01-31-07 06:11 PM
Hi,
if I execute the following commands will I reduce the size of this file?
osql -E
1> use cdr
2> go
1> backup log cdr with no_log
2> go
1> dbcc shrinkdatabase(cdr)
2> go
1>exit
Thanks,
Ruben
________________________________
De: Ryan Ratliff [mailto:rratliff@cisco.com]
Enviado el: mié 31/01/2007 15:32
Para: Ruben Montes (Europe)
CC: Joe Pollere (US); cisco-voip@puck.nether.net
Asunto: Re: [cisco-voip] CDR_log.LDF huge size
It may take a while but you can still enable BARS to back up your
CDRs. If your transaction log is filling up that quickly then it
sounds like you have a pretty hefty call volume and you have hit he
max amount of CDR records so Aupair is having to delete a lot of them
to bring you back down. The max records by default is 1.5 million
and is set via a service parameter for Database Layer Monitor (aka
Aupair).
There is a SQL job that will truncate the logs as well but it only
triggers if the c: drive gets below 500Mb free space.
-Ryan
On Jan 31, 2007, at 8:54 AM, Ruben Montes ((Europe)) wrote:
Hi,
BARS is actually not backing up the CDR. Can I still configure it now
or it's too late due to the size of the file?
Thanks,
Ruben
De: Joe Pollere (US) [mailto:Joe.Pollere@us.didata.com]
Enviado el: mié 31/01/2007 13:59
Para: Ruben Montes (Europe); cisco-voip@puck.nether.net
Asunto: RE: [cisco-voip] CDR_log.LDF huge size
Ruben,
You need to truncate the log file. There is a sql command to do it.
Alternatively if you back up with BARS select CDR and BARS will
truncate for you as part of the backup process.
Joe
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-
bounces@puck.nether.net] On Behalf Of Ruben Montes (Europe)
Sent: Wednesday, January 31, 2007 4:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CDR_log.LDF huge size
Hi,
I have noticed that my CDR_log.LDF file, that is located in C:
\Program Files\Microsoft SQL Server\MSSQL\Data has a size of 32GB and
is growing 5GB per week. I suppose there should be a bug behind, but
the for the moment I want to stop this growing...
Do you know if it is enough with putting the service parameter CDR
Enabled flag to false to stop collecting CDR information? Later on
I'll see how we will purge this because I assume it will be a CPU
intensive process...
I have a TAC case opened, but for the moment the engineer it is not
helping me very much...
Regards,
Ruben
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: CDR_log.LDF huge size |
 |
 |
|
|
01-31-07 06:11 PM
Yup, that looks like it's directly taken from Wes' old bug
Note that the db shrink will take a while to execute on a 32Gb =
transaction log.
-Ryan
On Jan 31, 2007, at 9:36 AM, Ruben Montes ((Europe)) wrote:
Hi,
if I execute the following commands will I reduce the size of this file?
osql -E
1> use cdr
2> go
1> backup log cdr with no_log
2> go
1> dbcc shrinkdatabase(cdr)
2> go
1>exit
Thanks,
Ruben
De: Ryan Ratliff [mailto:rratliff@cisco.com]
Enviado el: mi=E9 31/01/2007 15:32
Para: Ruben Montes (Europe)
CC: Joe Pollere (US); cisco-voip@puck.nether.net
Asunto: Re: [cisco-voip] CDR_log.LDF huge size
It may take a while but you can still enable BARS to back up your
CDRs. If your transaction log is filling up that quickly then it
sounds like you have a pretty hefty call volume and you have hit he
max amount of CDR records so Aupair is having to delete a lot of them
to bring you back down. The max records by default is 1.5 million
and is set via a service parameter for Database Layer Monitor (aka
Aupair).
There is a SQL job that will truncate the logs as well but it only
triggers if the c: drive gets below 500Mb free space.
-Ryan
On Jan 31, 2007, at 8:54 AM, Ruben Montes ((Europe)) wrote:
Hi,
BARS is actually not backing up the CDR. Can I still configure it now
or it's too late due to the size of the file?
Thanks,
Ruben
De: Joe Pollere (US) [mailto:Joe.Pollere@us.didata.com]
Enviado el: mi=E9 31/01/2007 13:59
Para: Ruben Montes (Europe); cisco-voip@puck.nether.net
Asunto: RE: [cisco-voip] CDR_log.LDF huge size
Ruben,
You need to truncate the log file. There is a sql command to do it.
Alternatively if you back up with BARS select CDR and BARS will
truncate for you as part of the backup process.
Joe
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-
bounces@puck.nether.net] On Behalf Of Ruben Montes (Europe)
Sent: Wednesday, January 31, 2007 4:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CDR_log.LDF huge size
Hi,
I have noticed that my CDR_log.LDF file, that is located in C:
\Program Files\Microsoft SQL Server\MSSQL\Data has a size of 32GB and
is growing 5GB per week. I suppose there should be a bug behind, but
the for the moment I want to stop this growing...
Do you know if it is enough with putting the service parameter CDR
Enabled flag to false to stop collecting CDR information? Later on
I'll see how we will purge this because I assume it will be a CPU
intensive process...
I have a TAC case opened, but for the moment the engineer it is not
helping me very much...
Regards,
Ruben
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: CDR_log.LDF huge size |
 |
 |
|
|
01-31-07 06:11 PM
Hi,
I have just shrink the database with the previous commands and it has reduce
d the size of the file from 31Gb to 500Kb without any problem!
We have noticed that the CCM's CPU in the server has increased to about 50%
usage during 4 to 5 minutes (RTM is great!) but it hasn't produced any effec
t in the call handling or any other application...
Thanks to everybody for the help,
Ruben
________________________________
De: Ryan Ratliff [mailto:rratliff@cisco.com]
Enviado el: mié 31/01/2007 15:40
Para: Ruben Montes (Europe)
CC: Joe Pollere (US); cisco-voip@puck.nether.net
Asunto: Re: [cisco-voip] CDR_log.LDF huge size
Yup, that looks like it's directly taken from Wes' old bug
Note that the db shrink will take a while to execute on a 32Gb
transaction log.
-Ryan
On Jan 31, 2007, at 9:36 AM, Ruben Montes ((Europe)) wrote:
Hi,
if I execute the following commands will I reduce the size of this file?
osql -E
1> use cdr
2> go
1> backup log cdr with no_log
2> go
1> dbcc shrinkdatabase(cdr)
2> go
1>exit
Thanks,
Ruben
De: Ryan Ratliff [mailto:rratliff@cisco.com]
Enviado el: mié 31/01/2007 15:32
Para: Ruben Montes (Europe)
CC: Joe Pollere (US); cisco-voip@puck.nether.net
Asunto: Re: [cisco-voip] CDR_log.LDF huge size
It may take a while but you can still enable BARS to back up your
CDRs. If your transaction log is filling up that quickly then it
sounds like you have a pretty hefty call volume and you have hit he
max amount of CDR records so Aupair is having to delete a lot of them
to bring you back down. The max records by default is 1.5 million
and is set via a service parameter for Database Layer Monitor (aka
Aupair).
There is a SQL job that will truncate the logs as well but it only
triggers if the c: drive gets below 500Mb free space.
-Ryan
On Jan 31, 2007, at 8:54 AM, Ruben Montes ((Europe)) wrote:
Hi,
BARS is actually not backing up the CDR. Can I still configure it now
or it's too late due to the size of the file?
Thanks,
Ruben
De: Joe Pollere (US) [mailto:Joe.Pollere@us.didata.com]
Enviado el: mié 31/01/2007 13:59
Para: Ruben Montes (Europe); cisco-voip@puck.nether.net
Asunto: RE: [cisco-voip] CDR_log.LDF huge size
Ruben,
You need to truncate the log file. There is a sql command to do it.
Alternatively if you back up with BARS select CDR and BARS will
truncate for you as part of the backup process.
Joe
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-
bounces@puck.nether.net] On Behalf Of Ruben Montes (Europe)
Sent: Wednesday, January 31, 2007 4:54 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] CDR_log.LDF huge size
Hi,
I have noticed that my CDR_log.LDF file, that is located in C:
\Program Files\Microsoft SQL Server\MSSQL\Data has a size of 32GB and
is growing 5GB per week. I suppose there should be a bug behind, but
the for the moment I want to stop this growing...
Do you know if it is enough with putting the service parameter CDR
Enabled flag to false to stop collecting CDR information? Later on
I'll see how we will purge this because I assume it will be a CPU
intensive process...
I have a TAC case opened, but for the moment the engineer it is not
helping me very much...
Regards,
Ruben
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
|
Sponsored Links |
 |
 |
|
|
 |
All times are GMT. The time now is 10:49 PM. |
 |
|
|
 |
|
 |
|
|
 |
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
|
|
|
|
Medical and Health forum | Computer Games Reviews | Graphics design forum
|
 |
|
 |
|