Please help....index corruption issue

  • Already tried repair, rebuild, detach/attach, backup/restore (no backup prior to this error).

    DBCC CHECKDB generates following error message

    Msg 8977, Level 16, State 1, Line 1

    Table error: Object ID 64719283, index ID 1, partition ID 285716419641344, alloc unit ID 285716419641344 (type In-row data). Parent node for page (1:84361) was not encountered.

    Msg 8934, Level 16, State 1, Line 1

    Table error: Object ID 64719283, index ID 1, partition ID 285716419641344, alloc unit ID 285716419641344 (type In-row data). The high key value on page (1:93719) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (1:84361).

    Much apprecaite it.

    Thank you.

  • Your corruption appears to be in a non-clustered index (indexID 1) - drop the index and recreate it.

    (Sorry, above info is wrong - indexID 1 = the c/i)

    dave

  • david.ames (6/26/2012)


    Your corruption appears to be in a non-clustered index (indexID 1) - drop the index and recreate it.

    dave

    Sorry, but IndexID 1 is the clustered index, not a nonclustered index. Do you have a current full backup and t-log/differential backups?

  • Do you have any way to recreate your data should you have to rebuild from scratch (which you may have to do in this case)?

  • Please run the following and post the full and complete output.

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    p.s. Detach/attach will never repair corruption and can actually make the situation worse.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    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

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply