I/O error on One Database File | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

I/O error on One Database File

Hello Guys I have one problem continuously occuring on my Database machine. I am running SQL Server 2000 Enterprise Edition.
The error is as follows: Error: 823, Severity:24, State:2
I/O Error 1450(Error not found) detected during read at offset 0x00000002cc000 in file ‘F:SU_Data.MDF’ The value of offset is always different whenever this error comes.I have go through the websites and findout with most cases that instead of (Error not found) they get the (insufficient resources) message. Can anyone check what might be possible reason for this. Thanks and Regards Mansoor
Take help of this KBAhttp://support.microsoft.com/default.aspx?scid=kb;en-us;828339 to resolve the issue and list out configuration of the h/w and SQL server settings for assessment. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I have go through the document and some other documents mentioned in that document. The problem in my case is that I am getting the message (Error not found), I am not getting any kind of error which are mentioned in these documents.
Actually in my scenario there is one application which try to get some results from this database file after every hour. Not all the time I am getting this message but 3 or 4 times in a day, I am getting this message. Thanks Mansoor
In that case refer to the event viewer for any h/w issues and collect PERFMON (SYSMON) counters for Physical disk, process, processor, memory and other SQL related counters to access the issue. Confirm the level of service pack on SQL & Windows. Books online clearly mentions action points for thsi error:
Check the accessibility and condition of the device in question. Run hardware diagnostics and correct problems, if possible. Restore damaged files from the latest database backup. Restoring from a database backup should always be considered the primary means of fixing a damaged database. If you don’t have a backup or if the errors detected are very isolated, the repair functionality of DBCC CHECKDB may be useful. However, using DBCC CHECKDB can be more time consuming than restoring the damaged files from a backup, and you may not be able to recover all your data

Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>