I/O error (torn page) detected during read

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

tulip - 31 Mar 2008 17:38 GMT

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

Reply to this Message

Andrew J. Kelly - 31 Mar 2008 18:11 GMT

Unless this is a nonclustered index your best bet is to restore from the
last known good backup. Do you have Torn Page Detection turned on for that
db? If not you should so you can spot issues like this sooner. In any case
have a look at this series from Paul Randal on checkdb and what your options
are.
http://www.sqlskills.com/blogs/paul/CategoryView,category,CHECKDB%2BFrom%2BEvery
%2BAngle.aspx

Signature

Andrew J. Kelly SQL MVP
Solid Quality Mentors

> we are running a maintainance plan on sql 2000 standard edition, got the
> error,
[quoted text clipped - 27 lines]
>
> please help. thanks

Reply to this Message

tulip - 31 Mar 2008 18:22 GMT

i found that the error is dated back to 2006, so the backup since then won't
be valid, right?

what does this mean: repair_allow_data_loss is the minimum repair level for
the errors found by DBCC CHECKDB (db_source noindex).

thank you

> Unless this is a nonclustered index your best bet is to restore from the
> last known good backup. Do you have Torn Page Detection turned on for that
[quoted text clipped - 34 lines]
> >
> > please help. thanks

Reply to this Message

Aaron Bertrand [SQL Server MVP] - 31 Mar 2008 18:37 GMT

> what does this mean: repair_allow_data_loss is the minimum repair level
> for
> the errors found by DBCC CHECKDB (db_source noindex).

It means that an attempt to repair the table may result in data loss, but
the only way you can try at all, is to allow for that to happen.

Reply to this Message