Post reply

Production Database in Suspect mode

  • December 19, 2009 at 1:02 am

    #156516

    Hi,

    Our production database is in Suspect mode after a disk failure. Please see the error messages in the error log. Please advice me what exact steps I need to follow now..

    2009-12-18 17:59:17.52 spid3s Error: 17053, Severity: 16, State: 1.

    2009-12-18 17:59:17.52 spid3s LogWriter: Operating system error Exception 0x2 encountered.

    2009-12-18 17:59:17.54 spid3s Error: 17308, Severity: 16, State: 1.

    2009-12-18 17:59:17.54 spid3s LogWriter: Process 3 generated an access violation. SQL Server is terminating this process.

    2009-12-18 17:59:17.57 spid3s Error: 17053, Severity: 16, State: 1.

    2009-12-18 17:59:17.57 spid3s LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.

    2009-12-18 17:59:17.57 spid3s Write error during log flush.

    2009-12-18 17:59:17.57 spid53 Error: 9001, Severity: 21, State: 4.

    2009-12-18 17:59:17.57 spid53 The log for database 'sharepoint_Config' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    2009-12-18 17:59:17.57 spid55 Error: 9001, Severity: 21, State: 4.

    2009-12-18 17:59:17.57 spid55 The log for database 'sharepoint_Config' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    thanks

  • December 19, 2009 at 1:46 am

    #1094420

    Please tell me that you have a backup of this database.

    Is that all of the errors in the error log?

    Can you check the windows event log for any disk-related errors.

    Do you know where the log file for that database is supposed to be? (query sys.master_files if you're not sure). Check that the drive is there and that the file is where it should be.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • December 19, 2009 at 2:28 am

    #1094423

    Hi Gail,

    Please tell me that you have a backup of this database.

    Yes, we have the backup

    Is that all of the errors in the error log?

    Yes, all the messages are from error log.

    After reading the error log messages, I have restarted the SQL Services and the database came online!

    Now the System admin looking into the drive failure issue.

    thank you

  • December 19, 2009 at 2:45 am

    #1094426

    So it looks like a transient IO failure. I would recommend doing lots of diagnostics on that drive, or even just consider replacing it. Intermittent IO failures are not pleasant.

    Please also run the following to make sure there are no lingering problems. If it produces any errors, post them here.

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • December 19, 2009 at 3:08 am

    #1094427

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    You mean run the below?

    DBCC CHECKDB (Database Name) WITH NO_INFOMSGS, ALL_ERRORMSGS

  • December 19, 2009 at 4:25 am

    #1094433

    Yeah, that's what I said. Replace the <Database Name> with the actual name of the database (in this case Sharepoint_Config)

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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