none
DPM Database Corruption in table tbl_TE_TaskTrail RRS feed

  • Question

  • I'm running DPM 2010 and noticed that my backup of the DPMDB stopped working. Unfortunately I noticed this a little bit late and it appears I do not have a valid backup of this database.

    When I run "dbcc checkdb (dpmdb) WITH NO_INFOMSGS;" I get the following results:

    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:4034), slot 2, text ID 240353411072 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:4034), slot 4, text ID 240353476608 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:7286), slot 2, text ID 238230700032 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:7286), slot 3, text ID 238230765568 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:7500), slot 13, text ID 234249781248 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:7500), slot 14, text ID 234249846784 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:13162), slot 1, text ID 251474608128 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:24852), slot 7, text ID 250053394432 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:37596), slot 13, text ID 248533549056 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:37596), slot 14, text ID 248533614592 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:63420), slot 6, text ID 251916255232 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:63420), slot 10, text ID 251916320768 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:81545), slot 3, text ID 255905562624 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:87692), slot 11, text ID 231486521344 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:87692), slot 12, text ID 231486586880 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:90511), slot 2, text ID 255905628160 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:100031), slot 5, text ID 251036499968 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:109958), slot 4, text ID 251036565504 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:112460), slot 10, text ID 243212419072 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:112460), slot 11, text ID 243212615680 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:114174), slot 3, text ID 231400210432 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:114174), slot 4, text ID 231400275968 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:120735), slot 12, text ID 251474411520 is not referenced.
    Msg 8964, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047037440 (type LOB data). The off-row data node at page (1:150761), slot 9, text ID 250053459968 is not referenced.
    Msg 8928, Level 16, State 1, Line 1
    Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047168512 (type In-row data): Page (1:13866) could not be processed.  See other errors for details.
    Msg 8939, Level 16, State 98, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047168512 (type In-row data), page (1:13866). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 79824905 and -4.
    Msg 8939, Level 16, State 98, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047168512 (type In-row data), page (1:13866). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 79824905 and -4.
    Msg 8976, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047168512 (type In-row data). Page (1:13866) was not seen in the scan although its parent (1:20093) and previous (1:65535) refer to it. Check any previous errors.
    Msg 8978, Level 16, State 1, Line 1
    Table error: Object ID 530100929, index ID 1, partition ID 72057594044743680, alloc unit ID 72057594047168512 (type In-row data). Page (1:59738) is missing a reference from previous page (1:13866). Possible chain linkage problem.
    CHECKDB found 0 allocation errors and 29 consistency errors in table 'tbl_TE_TaskTrail' (object ID 530100929).
    CHECKDB found 0 allocation errors and 29 consistency errors in database 'DPMDB'.
    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DPMDB).

    As far as I can tell DPM is functioning properly, however, I would like to repair the database. Ironically, it appears that I do not have a good backup of the database to restore from.  When I query all the data in the is table: "SELECT * FROM tbl_TE_TaskTrail" it doesn't error out and contains 93,482 rows.

    My questions is, what does the tbl_TE_TaskTrail hold, and how do I go about repairing this table?

    Monday, September 10, 2012 3:28 PM

Answers

  • I ran a backup of the database and then restored the database. After doing this I ran the "dbcc checkdb" command again and this time it did not return any errors.

    I'm still curious what the tbl_TE_TaskTrail holds. Especially if there was loss of data during this procedure. This way I know what I might expect in the future if I run into other issues.
    • Edited by rpanna Tuesday, September 11, 2012 1:58 PM
    • Marked as answer by rpanna Tuesday, September 11, 2012 1:58 PM
    Tuesday, September 11, 2012 1:56 PM
  • Hi,

    tbl_TE_TAskTrail is the history of all DPM jobs that ran or failed.  It is used to populate the JOBS tab.  We maintain 30 days worth of job history and it's pruned nightly to delete jobs history older than 30 days.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by rpanna Tuesday, September 11, 2012 8:39 PM
    Tuesday, September 11, 2012 5:52 PM
    Moderator

All replies

  • Hi

    Does event viewer yield any information if DPM is crashing because the DB is too big?

    If you check the DPM error log what else does it tell you?

    You can make a backup of the DB "dpmbackup –db " before carrying on.

    Also check if you have the latest patches and Service pack for DPM

    Monday, September 10, 2012 4:19 PM
  • I ran a backup of the database and then restored the database. After doing this I ran the "dbcc checkdb" command again and this time it did not return any errors.

    I'm still curious what the tbl_TE_TaskTrail holds. Especially if there was loss of data during this procedure. This way I know what I might expect in the future if I run into other issues.
    • Edited by rpanna Tuesday, September 11, 2012 1:58 PM
    • Marked as answer by rpanna Tuesday, September 11, 2012 1:58 PM
    Tuesday, September 11, 2012 1:56 PM
  • From what i understand tbl_TE_TaskTrail holds entries for tasks. Almost like a Garbage collection.
    Tuesday, September 11, 2012 4:58 PM
  • Hi,

    tbl_TE_TAskTrail is the history of all DPM jobs that ran or failed.  It is used to populate the JOBS tab.  We maintain 30 days worth of job history and it's pruned nightly to delete jobs history older than 30 days.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by rpanna Tuesday, September 11, 2012 8:39 PM
    Tuesday, September 11, 2012 5:52 PM
    Moderator