November 18, 2005 at 1:54 am
Hi all,
Can someone tell me what the following error points to
I/O error 33(The process cannot access the file because another process has locked a portion of the file.) detected during write at offset 0x000006eb372000 in file 'd:\Data\dsd41tst.mdf'..
the severity is 24
Error: 823, Severity: 24, State: 4
thanks in advance
Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me
November 18, 2005 at 6:29 am
Check for an anti-virus program.
The usual practice is to exclude database files from virus scans which are files with extention *.mdf, *.ndf or *.ldf
SQL = Scarcely Qualifies as a Language
November 21, 2005 at 4:14 am
Hi,
I am getting this error continously. Infact it fills my SQL server error log, but the database is running fine.
It has Windows System Error Code - 033 (33 ERROR_LOCK_VIOLATION). The process cannot access the file because another process has locked a portion of the file.
when window encounters this error does it write to error log of SQL. If so what revelance does this error have? anti virsus program?
But today the database is marked Suspect. (clearly I/O error)
Pl explain. Thanks in advance
Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me
November 24, 2005 at 10:23 am
Because your DB has gone suspect, its possible the virus scanner (or whatever was lockign the file) has caused SQL Server to throw the DB offline.
Can you post the output of
DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS
If there's no corruption, you should be able to reset the suspect status and continue. Are there any indications of h/w problems in the errorlog or Windows event logs?
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
November 25, 2005 at 2:44 pm
The original error indicates that the SQL server encountered some type of write error (delayed or otherwise, depending on hardware). If this is indeed the case, the database is probably corrupt and will need to be restored to an image prior to the error. Run a complete DBCC CHECKDB as suggested above...
In addition to a virus scanner, this could be a tape backup as well, locking one file (of a multi-file) of a database during an I/O write by the SQL server. It could also be hardware going south and an o/s level array driver invoking some kind of software raid copy...
Your friendly High-Tech Janitor... 🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply