|
Home > Archive > Voice over IP Cisco > October 2006 > Unity drive filling up
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Unity drive filling up
|
|
| Gary L. Pate 2006-10-30, 7:12 pm |
| I have a customer who keeps running into the issue of running out of disk
space because of the SQL logs. I had opened a TAC case, and we ran a
procedure to reduce this and that worked fine, and they also stated that the
normal Unity backup should be reducing this log file which doesn't seem to
be happening. They are running Backup exec 10d Rev. 5629. Does anyone know
if there is an issue with this version, and what I need to do to ensure the
log files are being reduced? Also, can these be moved to another drive with
more space?
Here is the procedure I followed to reduce the file:
CDrive filling up and the Event Viewer has the following error:
Error: 9002, Severity: 17, State: 6
The log file for database 'ReportDb' is full. Back up the transaction log
for the database to free up some log space.
1st. You need to ensure that Unity is being backed up, which causes the .log
files to shrink. If not, you can run the following procedure to shrink the
log file.
How to Squeeze UnityDB if it grows to large:
1. Bring up command prompt
2. osql -E
3. use unitydb
4. go
5. backup log unitydb with no_log
6. go
7. dbcc shrinkdatabase(unitydb)
8. go
9. exit
Example:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\WINNT>osql -E
1> use Unitydb
2> go
1> backup log unitydb with no_log
2> go
1> dbcc shrinkdatabase(unitydb)
2> go
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
------ ------ ----------- ----------- ----------- --------------
6 1 1192 80 1184 1184
6 2 63 63 56 56
(2 rows affected)
DBCC execution completed. If DBCC printed error messages, contact your
system
administrator.
1> exit
C:\WINNT>osql -E
1> use reportdb
2> go
1> backup log reportdb with no_log
2> go
1> dbcc shrinkdatabase(reportdb)
2> go
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
------ ------ ----------- ----------- ----------- --------------
5 1 376 80 352 352
5 2 63 63 56 56
(2 rows affected)
DBCC execution completed. If DBCC printed error messages, contact your
system
administrator.
1> exit
| |
| Rasim Duric 2006-10-30, 7:12 pm |
| I think the SQL Server Agent is not running on your Unity server. The
two jobs, SQLNihgtlyBackupJob and SQLWeeklyBackupJob should truncate the
log files. We had the same issue since we upgraded MSDE to SP4. Every
time we restart Unity we need manually start the SQL Server Agent on the
boxes with MSDE SP4.
You could move the DB and log files to another drive.
Rasim Duric
Network Analyst (CCS)
University of Guelph
Guelph, N1G 2W1, ON
519-824-4120x53146
rduric@uoguelph.ca
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Gary L. Pate
Sent: Monday, October 30, 2006 1:56 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Unity drive filling up
I have a customer who keeps running into the issue of running out of
disk
space because of the SQL logs. I had opened a TAC case, and we ran a
procedure to reduce this and that worked fine, and they also stated that
the
normal Unity backup should be reducing this log file which doesn't seem
to
be happening. They are running Backup exec 10d Rev. 5629. Does anyone
know
if there is an issue with this version, and what I need to do to ensure
the
log files are being reduced? Also, can these be moved to another drive
with
more space?
Here is the procedure I followed to reduce the file:
CDrive filling up and the Event Viewer has the following error:
Error: 9002, Severity: 17, State: 6
The log file for database 'ReportDb' is full. Back up the transaction
log
for the database to free up some log space.
1st. You need to ensure that Unity is being backed up, which causes the
..log
files to shrink. If not, you can run the following procedure to shrink
the
log file.
How to Squeeze UnityDB if it grows to large:
1. Bring up command prompt
2. osql -E
3. use unitydb
4. go
5. backup log unitydb with no_log
6. go
7. dbcc shrinkdatabase(unitydb)
8. go
9. exit
Example:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\WINNT>osql -E
1> use Unitydb
2> go
1> backup log unitydb with no_log
2> go
1> dbcc shrinkdatabase(unitydb)
2> go
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
------ ------ ----------- ----------- ----------- --------------
6 1 1192 80 1184 1184
6 2 63 63 56 56
(2 rows affected)
DBCC execution completed. If DBCC printed error messages, contact your
system
administrator.
1> exit
C:\WINNT>osql -E
1> use reportdb
2> go
1> backup log reportdb with no_log
2> go
1> dbcc shrinkdatabase(reportdb)
2> go
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
------ ------ ----------- ----------- ----------- --------------
5 1 376 80 352 352
5 2 63 63 56 56
(2 rows affected)
DBCC execution completed. If DBCC printed error messages, contact your
system
administrator.
1> exit
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|