Post reply

msdb in suspect mode

  • May 14, 2007 at 9:51 pm

    #177960

    hello,

    Thanks for the help ahead of time..much appreciated...so here is the situation

    my msdb is in suspect mode... and yes i have done the exec sp_resetstatus and then when i run dbcc checkdb.  i get the error that the db is in suspect mode.  So i look and say hmmmmm then stop and start the services....and the db shows ok... so i then think all is well but nope when i try to access it i get the same thing again.  error saying db is in suspect mode but visually it dont appear to be (meaning the suspect is not next to the name).  I have about 36 GB free on the server so its not a space issue.

    If i can get any assistance please feel free to give comments.  Once again thanks

    Darryl

    DHeath

  • May 14, 2007 at 11:00 pm

    #706381

    Can try to recover the db using dbcc dbrecover(msdb)

  • May 14, 2007 at 11:14 pm

    #706386

    thanks for the suggestion..and i tried using that and still remained in suspect mode.

    Now just to add here... this is a backup server.  So currently it has the same msdb as the source...and that msdb has NO issues.   If i copy it over it continues to go back into suspect mode if not immediately within the hour.

    Any ideas...thanks for any thought processes

    DHeath

  • May 14, 2007 at 11:19 pm

    #706387

    any thing found on sql error log or event viewer?

  • May 14, 2007 at 11:34 pm

    #706388

    keeps saying there is an error when redoing logged operation in database 'msdb'...Error at log record id (7603:329:3)

    And then after i tried the dbrecover - the logg is could not recover. Contact DBA

    Thanks again

    DHeath

  • May 16, 2007 at 8:23 am

    #706813

    Is this happens with only msdb database or other too?

    If this issue is also with the other DB then, I think you need to check the hardware of the backup server.

    Minaz Amin

    "More Green More Oxygen !! Plant a tree today"

  • May 16, 2007 at 5:47 pm

    #706966

    The situation has come to an end..finally....after long hard searching and working and ...and...and ..    Anyways..

    The SQL Server of the prod and backup server were different.  Both SP4 but different builds one was 2039 the other 2162(gotta look beyond the trees).  This was the major cause because all system datases are transfer to the backup as well.  The fix was to get on the same build level and then that seemed to take care of it.

    Lesson learned as to look even deeper then the SP level but the build level as well. 

    Thanks for all the help much appreciated.  After finding the issue i realized that sometimes we are over looking the obvious. 

    DHeath

Viewing 7 posts - 1 through 6 (of 6 total)

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