Post reply

MSDB errors.

  • March 17, 2004 at 9:53 am

    #65117

    I just started receiving the following errors related to "msdb". Any suggesitons how to resolve the problem much appreciated. (Note the error related to table  "backupmediafamily". Incidentally, the nightly backups claim to be OK.)

    TIA,

    Bill

     

     

    17] Database msdb: Check Data and Index Linkage...

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 2511: [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 146099561, Index ID 2. Keys out of order on page (1:2010), slots 41 and 42.[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediafamily' (object ID 146099561).[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in database 'msdb'.[Microsoft][ODBC SQL Server Driver][SQL Server]repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).

        The following errors were found:

    [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 146099561, Index ID 2. Keys out of order on page (1:2010), slots 41 and 42.

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediafamily' (object ID 146099561).

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in database 'msdb'.

    [Microsoft][ODBC SQL Server Driver][SQL Server]repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).

        ** Execution Time: 0 hrs, 0 mins, 8 secs **

  • March 19, 2004 at 10:56 am

    #499551

    Maybe the following will work.

    a.  Backup MSDB

    b.  Start SQL Server in single user mode

    c.  Stop SQL Server Agent

    d. Run DBCC CHECKDB ('msdb',repair_rebuild) with all_errormsgs

    BOL says of "repair_rebuild" performs all repairs done by REPAIR_FAST and includes time-consuming repairs such as rebuilding indexes. These repairs can be done without risk of data loss.

    e. if step d appears successful, I would run "DBCC CHECKDB ('msdb') with all_errormsgs" (like a double check)

    f. Stop SQL Server

    g. Start SQL Server (restore MSDB if above process is not successful)

    h. Start SQL Server Agent

    Best Wishes

    GaryA

     

Viewing 2 posts - 1 through 1 (of 1 total)

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