March 16, 2002 at 3:40 am
I have a huge production database over 30GB, the log file looks corrupt (Error: 823, Severity: 24, State: 10)and the db is marked suspect. I tried detaching and just attaching the data portion to a new db but looking at the errorlog it seems to want to open the log as well.
Any ideas ?
March 16, 2002 at 6:36 am
From BOL
Error 823
Severity Level 24
Message Text
I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.
Explanation
Microsoft® SQL Server™ encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved.
Action
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 .
Caution If running DBCC CHECKDB with one of the repair clauses does not correct the problem or if you are unsure how this process may affect your data, contact your primary support provider.
I suggest running checkdsk utility for drive. Open My Computer, right click the drive in question, choose properties, the goto the tools tab, and press check now.
Here check "Scan for and attempt to recover bad sectors" but not "Automatically fix file system errors" as you want to see these.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply