Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 I/O error (torn page) detected during read

Author  Topic 

maryxu
Starting Member

36 Posts

Posted - 2008-03-31 : 12:36:20
we are running a maintainance plan on sql 2000 standard edition, got the error,

[2] Database db_source: Check Data Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page (1:197116) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1221579390, index ID 0, page (1:197116).
Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in table 'xxx'(object ID 1221579390).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in database 'db_source'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (db_source noindex).

when i run query on anlyzer select * from xxx, i got the error
Server: Msg 823, Level 24, State 2, Line 1
I/O error (torn page) detected during read at offset 0x000000603f8000 in file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.

Connection Broken

please help. thanks

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-03-31 : 12:43:01
Check this out:

http://support.microsoft.com/kb/828339

http://sql-server-performance.com/Community/forums/t/4151.aspx
Go to Top of Page

maryxu
Starting Member

36 Posts

Posted - 2008-03-31 : 13:00:17
so does the backup is good? can i restore use the latest backup? thanks

quote:
Originally posted by sodeep

Check this out:

http://support.microsoft.com/kb/828339

http://sql-server-performance.com/Community/forums/t/4151.aspx


Go to Top of Page

maryxu
Starting Member

36 Posts

Posted - 2008-03-31 : 13:19:09
what does this mean: repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (db_source noindex).

quote:
Originally posted by sodeep

Check this out:

http://support.microsoft.com/kb/828339

http://sql-server-performance.com/Community/forums/t/4151.aspx


Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-03-31 : 13:54:54
Where your backups are stored? Is it in your disk or tape? I would get the latest backup from tapes in offsite location since it is issues related to Hardware/Drives?
Go to Top of Page

maryxu
Starting Member

36 Posts

Posted - 2008-03-31 : 15:56:17
if this error has been ongoing for a while, does the daily still good? thanks
quote:
Originally posted by sodeep

Where your backups are stored? Is it in your disk or tape? I would get the latest backup from tapes in offsite location since it is issues related to Hardware/Drives?

Go to Top of Page

maryxu
Starting Member

36 Posts

Posted - 2008-03-31 : 15:57:10
quote:
Originally posted by maryxu

if this error has been ongoing for a while, does the daily backup still good? thanks
quote:
Originally posted by sodeep

Where your backups are stored? Is it in your disk or tape? I would get the latest backup from tapes in offsite location since it is issues related to Hardware/Drives?



Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-31 : 22:08:12
>> what does this mean: repair_allow_data_loss is the minimum repair level for the errors

That means you can try repair the db with that option, but may lose data.

>> if this error has been ongoing for a while, does the daily still good?

You need restore most recent backup to new db with another name, run dbcc against it. If get same error, restore backup from one day before until get good one.
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-04-01 : 03:03:47
Running CHECKDB with REPAIR_ALLOW_DATA_LOSS will definitely be able to fix this issue - but to for this error it will simply delete the broken page. In this case, the page is a data page so will definitely lose data.

If you have a backup, you should restore from it to avoid losing data.

A torn-page (as referenced in the error) can happen when a power-failure occurs during transaction processing and one of the drives loses power in the middle of a write operation. Did you have a power failure?

Thanks

Paul Randal
Managing Director, SQLskills.com
Go to Top of Page

surya_rakanta
Starting Member

19 Posts

Posted - 2008-07-31 : 02:44:56
when i run query on anlyzer select * from xxx, i got the error
Server: Msg 823, Level 24, State 2, Line 1
I/O error (torn page) detected during read at offset 0x000000603f8000 in file 'F:\Program Files\Microsoft SQL Server\MSSQL\data\db_Data.MDF'.
------
If you are using MS SQL 2000 database, by using hex editor program, it is possible to manually fix the torn bits.

To save time, I have an article regarding this. Check it out.

God didn't do this, Anna, WE did.
— Robert Neville in I am Legend.
Go to Top of Page
   

- Advertisement -