October 3, 2007 at 6:43 am
Hi
The log of one of the databases shows the following message
I/O error (torn page) detected during read at offset 0x00000ae2b64000 in file 'G:\MSSQL2000\MSSQL\Data\messages_Data.MDF'.
What needs to be done to rectify this?
Can anyone advice?
Thanks and regards
Sandhya
October 3, 2007 at 7:03 am
This is a severe error, and indicates that the db is likely in an incosistent state (suspect/corrupt)
-- quote BOL --
If a torn page is detected, an I/O error is raised and the connection is killed. If the torn page is detected during recovery, the database is also marked suspect. The database backup should be restored, and any transaction log backups applied, because it is physically inconsistent.
-- end quote --
/Kenneth
October 3, 2007 at 7:31 am
Kenneth,
Thanks for your immediate reply.. But the database is not in the Suspect Mode.. And I must confess that it is my negligence as I am getting this message for the third time and I didn't take much care as it is a Dev server.. But concerned as this DB may soon migrate to Prod..
What needs to be ensured before the migration?
October 3, 2007 at 7:45 am
A torned page detected is a sign of hardware malfunction or some other unexpected event preventing a write to the database to complete in a clean way.
If you depend on the data in a db where this has occured, it's basically corrupt.
The course of action is to find out why it happened.
ie - is there some bad hardware that needs to be replaced?
Do you have a controller without a battery? Or is the battery empty?
Restore your latest good backup.
This is not a 'fixable' error.
Also, look up 'TORN_PAGE_DETECTION' in BOL, where there is more info.
/Kenneth
October 3, 2007 at 1:08 pm
And you need to fix the hardware! It's a problem that tends to get worse.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply