checkdb error on index ID 0

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Data Corruption » checkdb error on index ID 0

checkdb error on index ID 0

Rate Topic

Display Mode

Topic Options

Author

Message

David Kang

Posted Monday, December 03, 2012 12:10 PM

SSC Rookie

Group: General Forum Members
Last Login: Monday, December 10, 2012 1:04 PM
Points: 29, Visits: 118

I need help on fixing checkdb error.

Here's the output of checkdb:

Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1627389056, index ID 0, page ID (1:611861). The PageId in the page header = (14131:894586624).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:611862). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:611863). The PageId in the page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611860) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 226099846, index ID 0, page (1:611860). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611861) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611862) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611863) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1627389056)' (object ID -1627389056).
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 5 consistency errors in table 'REQ_ITEM' (object ID 226099846).
CHECKDB found 0 allocation errors and 8 consistency errors in database 'PMM'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PMM ).

It's running on SQL 2000 SP3.
Can I repair these errors with 'REPAIR_REBUILD'?

Thanks in advance,
David.

Post #1392105

GilaMonster

Posted Monday, December 03, 2012 12:51 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725, Visits: 29,981

David Kang (12/3/2012)

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PMM ).

Since repair allow data loss is the minimum repair level necessary, running checkDB with any lesser repair level will be a waste of time. Minimum repair level is exactly that.

You will lose data. Four pages of data from the table REQ_ITEM.

I assume there's no good backup available...

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1392119

David Kang

Posted Monday, December 03, 2012 1:10 PM

SSC Rookie

Group: General Forum Members
Last Login: Monday, December 10, 2012 1:04 PM
Points: 29, Visits: 118

Gail! Thanks for quick response.

So, can I run page level restore for this? or restore the whole DB to temp location then extract the 'REQ_ITEM' table?

Thanks again,
David.

Post #1392123

GilaMonster

Posted Monday, December 03, 2012 3:33 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725, Visits: 29,981

If you have a clean backup (one without any corruption) and an unbroken chain of log backups up to present, you can do a page restore. Or you can restore the full backup over the DB followed by all log backups to bring the DB back to current time with no corruption (take a tail-log backup first).

If the DB is not in full recovery or you don't have the necessary log backups, then you're looking at either losing data by restoring to the last good backup or by repairing. You can, in that case, try to repair then restore a copy of the DB elsewhere and sync in the missing data.

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1392167

jonmichel72

Posted Wednesday, December 05, 2012 12:15 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, February 07, 2013 5:14 AM
Points: 4, Visits: 2

Now a Days, when you search on the Google, many companies providing a data recovery services as well as recovery software. In such types of software one is recoveryfix for sql repair software, this company offering a free trial version software, with the help of this trial version you can see the preview of recoverable data.

Thanks

Post #1392810

opc.three

Posted Wednesday, December 05, 2012 11:13 PM

SSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 9:55 PM
Points: 6,720, Visits: 11,759

Since you're on SQL 2000 you do not have the option of doing page restores. As Gail outlined, you can restore from backup that do not include the corruption (including tail-log) to bring the database to current or look into bringing up a parallel copy of the database that does not include the corruption to recover the data manually, or do the repair allowing for data loss.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato

Believe you can and you're halfway there. --Theodore Roosevelt

Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein

The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein

1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy

Post #1393328

David Kang

Posted Monday, December 10, 2012 1:15 PM

SSC Rookie

Group: General Forum Members
Last Login: Monday, December 10, 2012 1:04 PM
Points: 29, Visits: 118

Thanks both.

After I ran the checkDB with allow data loss, there were 100 rows are missing on REQ_ITEM table.
Since it was only affected single table, I was restore from last good backup and re-inserted missing data back to REQ_ITEM table.

Thanks again,
David.

Post #1394766

« Prev Topic | Next Topic »

Permissions