DBCC Errors on MSDB database 1

[Ovatvvon]

Hello,

For the last two days we've been receiving DBCC errors on our MSDB database during Opt jobs. A manual DBCC check reveils the errors below, along with the message that a Repair with data loss is a the minimum action required. A few of the DBA's here think it would just be better to restore the MSDB from a good backup from a few days ago, as they do not think there were any significant changes in the last day or two.

Does anyone have any input on whether it would be better to do a repair, or just restore the system database? Also, are there any extra tasks that would have to be performed during / after the restore - since it is a system database (as I have not had to restore a system database before), or is it just as simple as restoring a user database?

Server: Msg 8951, Level 16, State 1, Line 1
Table Corrupt: Table 'backupset' (ID 194099732). Missing or invalid key in index 'backupsetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:3539:14) identified by (RID = (1:3539:14) backup_set_id = 226935) has index values (backup_set_uuid = 80B83852-5DD3-403E-88D8-C07949B42980€gR´
 and backup_set_id = 226935).
Server: Msg 8910, Level 16, State 1, Line 1
Page (1:161) in database ID 4 is allocated to both object ID 914102297, index ID 1, and object ID 914102297, index ID 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table Corrupt: Object ID 914102297, index ID 1. B-tree page (1:161) has two parent nodes (1:370), slot 27 and (1:370), slot 1.
Server: Msg 8975, Level 16, State 1, Line 1
Page referenced by more than one page: Object ID 914102297, index ID 1. Page (1:1028)->next is an unmatched linkage to page (1:135). (1:1028)->next matches the previous linkage of the page.
Server: Msg 8978, Level 16, State 1, Line 1
Table Corrupt: Object ID 914102297, index ID 1. Page (1:1133) is missing a reference from previous page (1:161). Possible chain linkage problem.
Server: Msg 8935, Level 16, State 1, Line 1
Table Corrupt: Object ID 914102297, index ID 1. The previous link (1:2196) on page (1:1169) does not match the previous page (0:1) that the parent (1:370), slot 60 expects for this page.
Server: Msg 8979, Level 16, State 1, Line 1
Table Corrupt: Object ID 914102297, index ID 1. Page (1:1171) is missing references from parent (unknown) and previous (page (1:1028)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8977, Level 16, State 1, Line 1
Table Corrupt: Object ID 914102297, index ID 2. Parent node for page (1:3920) was not encountered.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupset' (object ID 194099732).
CHECKDB found 1 allocation errors and 6 consistency errors in table 'sysdbmaintplan_history' (object ID 914102297).
CHECKDB found 1 allocation errors and 7 consistency errors in database 'msdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

-Ovatvvon :-Q

 

[ptheriault]

If you look up DBCC CHECKDB in BOL there is a note by microsoft. It states to use the REPAIR options only as a last resort. They recommend restoring from a backup because the repair options do not consider any contraints that may exist on or between tables. also the restore of msdb is the same as with any user db. MSDB is usually a very small db so it won't take long either.

- Paul
- Database performance looks fine, it must be the Network!

 

[Ovatvvon]

Great. Thanks for the info!

-Ovatvvon :-Q