SQL Server Performance

Consistency errors in a Raiser's Edge db

Discussion in 'General DBA Questions' started by Khernunnous, Jul 29, 2009.

  1. Khernunnous New Member

    Hi all,
    I have a Raiser's Edge db that is running on SQL 2000 express. Its throwing the following consistency errors and I'm at a loss as to what to do. Blackbaud's proposal is to copy out about 20% of the existing tables into a new db where we would effectively loose 8+ years of data. Any direction you could provide would be really appreciated! It seems to me that there are really only two records causing issue here. Being able to determine which they are and deleting them would be totally acceptable if that's a viable solution.
    Msg 8944, Level 16, State 28, Server BROTHERRE_EXPRESS, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 294014618304512 (type Unknown), page (1:106760), row 21. Test (!(hdr->r_tagA & (VERSION_MASK | RECTAG_RESV_B))) failed. Values are 41 and 129.

    Msg 8944, Level 16, State 12, Server BROTHERRE_EXPRESS, Line 1
    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 294014618304512 (type Unknown), page (1:106760), row 21. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 41316 and 1886.
    Msg 8944, Level 16, State 28, Server BROTHERRE_EXPRESS, Line 1

    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 294014618304512 (type Unknown), page (1:106760), row 21. Test (!(hdr->r_tagA & (VERSION_MASK | RECTAG_RESV_B))) failed. Values are 41 and 129.
    Msg 8944, Level 16, State 12, Server BROTHERRE_EXPRESS, Line 1


    Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 294014618304512 (type Unknown), page (1:106760), row 21. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 41316 and 1886.

    CHECKDB found 0 allocation errors and 4 consistency errors not associated with any single object.
    Msg 8928, Level 16, State 1, Server BROTHERRE_EXPRESS, Line 1
    Object ID 1993058136, index ID 1, partition ID 72057594404405248, alloc unit ID 71906736119218176 (type LOB data): Page (1:106760) could not be processed. See other errors for details.


    CHECKDB found 0 allocation errors and 1 consistency errors in table 'ACTIONS' (object ID 1993058136).
    CHECKDB found 0 allocation errors and 5 consistency errors in database 'RE7Production'.
    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (RE7Production, noindex).
  2. RDW2 New Member

    Do you have clean back up, i.e. a back up of the database when it was not throwing these errors? Do you have the tranlog backups from that backup forward to this point?
    If the answer to both of those questions is "Yes", then you can restore the last clean back up and then roll it forward using the tran logs. Now, that may take a while but it should recover the entirety of your data.
    On the other hand, if the answer to the first question is that you do not have a clean backup . . . well, do you know the adage about being up a particular creek with inadequate means of locomotion?
    If you have a clean back up but not the tranlog backups, well, lets just say that you would be up only a slightly different creek.

Share This Page