Post reply

Help with DBCC Results

  • July 1, 2005 at 3:17 pm

    #165241

    First let me thank all of you who helped me this week.  It has been a truly craptacular week.

    I have DBCC CHECKDB results that show errors.  Here is an example:

    DBCC results for 'TABLENAME'.

    There are 2115 rows in 9 pages for object 'TABLENAME'.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 48719226, index ID 0: Page (1:4596656) could not be processed. See other errors for details.

    Server: Msg 8944, Level 16, State 1, Line 1

    Table error: Object ID 48719226, index ID 0, page (1:4596656), row 10. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 68 and 580.

    Server: Msg 8928, Level 16, State 1, Line 1

    Object ID 48719226, index ID 0: Page (1:5364884) could not be processed. See other errors for details.

    Server: Msg 8944, Level 16, State 1, Line 1

    Table error: Object ID 48719226, index ID 0, page (1:5364884), row 5. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 68 and 580.

    Server: Msg 2511, Level 16, State 1, Line 1

    Table error: Object ID 48719226, Index ID 1. Keys out of order on page (1:3954482), slots 381 and 382.

    How do you go about fixing these issues?  The repair options failed to repair any of them.  Is there a way you go about locating them?

  • July 1, 2005 at 4:37 pm

    #570463

    For a table this small, I'd script the table, indexes, and triggers then drop the indexes and triggers, copy out the data, rebuild everything and reload the data.

     

    The errors on index id 0 mean that the table has some corruption, so unloading (if you can) and loading it back may be your only option. 

    And then again, I might be wrong ...
    David Webb

  • July 5, 2005 at 7:10 am

    #570849

    I agree, for a table with only 2000 rows, your best bet would be to copy out the data to a separate table, then apply the index. You could simply drop the original table and rename the new one if you'd like or follow Mr. Webb's advice on scripting it and then dropping/recreating it.

    Cheers,

    Alex

    Rogue DBA

  • July 5, 2005 at 1:15 pm

    #570988

    Agree with David if its this small and only one table

    In bad situations I've also handle it this way - bcp out the data that I can, restore the last good backup, or rebuild from script the damaged tables  and then bcp the good data back in.

    Good luck and give a holler if you need more help

    Zach

     


    John Zacharkan

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

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