I'd look at the log file size for master and msdb. Is there any
possibility that these are on the C: Drive, and their logs of jobs (or
size caps) are the actual issue?
I would also consider running a job immediately prior to the restore
kicking off that logs the free space on the C: and D: drives.
==+==+==+==+==+==+==+==+==+==+==
Brendt W. Hess
Database Administrator, Motosport, Inc
brendt.[Email address protected]
==+==+==+==+==+==+==+==+==+==+==
-----Original Message-----
From: Louis Botes
[mailto:mssqldba-ezmlmshield-x50184120.[Email address protected]
Sent: Sunday, December 30, 2007 10:52 PM
To: LazyDBA Discussion
Subject: Weird Issue on SQL Server 2000
Hi All,
I trust you had a great Christmas and are all getting ready for new
years eve...
I hope there is someone out there picking up emails at this time of the
day ;)
I have a very weird issue on one of my standby servers. I perform log
shipping to this server every 15 minutes and then a complete backup from
one of my production servers is copied across each morning at around 2
am. The last transaction log is restored at 22:00 the previous evening.
A few of these databases seems to experience a timeout during the
restore and this leaves their status as Loading. This is fine, however
the real issue I have right now is the server then terminates with the
following sequence of events as listed in the Application Log for the
server:
17053 :
D:\sql\data\pre_dial_new.ldf: Operating system error 112(There is not
enough space on the disk.) encountered.
17053 :
LogWriter: Operating system error 112(There is not enough space on the
disk.) encountered.
Error: 9001, Severity: 21, State: 4
The log for database 'master' is not available.
Error: 3449, Severity: 21, State: 1
An error has occurred that requires SQL Server to shut down so that
recovery can be performed on database ID 1.
17053 :
LogWriter: Operating system error 112(There is not enough space on the
disk.) encountered.
Error: 9001, Severity: 21, State: 4
The log for database 'msdb' is not available.
At this point SQL Server doesn't start up and I have to manually restart
the service nearly every morning to get it back up and running.
Looking at the errors in the Application log it seems logical that I
have a disk space issue. However I have 61 GB free on the D: drive, the
database files are only about 13GB in size (When looking at the total
database log size on the production server I get the information from it
is just over 12.2 GB for the log and about 800MB for the data)
The C: drive on the machine has about 4GB free - this has remained
virtually the same for the past 12 months and the issue has only started
about a month ago.
I am running windows 2000 server, SP4 and SQL Server 2000 Standard
Edition, SP4.
Let me know if anyone has any useful ideas for me please??
------------------------------------------------------------------------
------------------
This e-mail was checked by the Verizon Business Internet Mail Content
Filtering Service.
The I M C F provides you with upstream anti-spam and content filtering
and multi layered virus protection.
For more information please contact your Verizon Business account
manager or the sender of this e-mail!!
------------------------------------------------------------------------
------------------
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
MS Sql Server LazyDBA home page