SQL Server detected a logical consistency-based I/O error : SQL 2005

  • Getting this:

    Msg 926, Level 14, State 1, Line 2

    Database 'DM_m000003_m000002_qdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

    Msg 5069, Level 16, State 1, Line 2

    ALTER DATABASE statement failed.

    Msg 824, Level 24, State 2, Line 2

    SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x627c02d9; actual: 0xb59aada1). It occurred during a read of page (1:6587397) in database ID 9 at offset 0x00000c9080a000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\DM_m000003_m000002_qdb.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

    Msg 3313, Level 21, State 2, Line 2

    During redoing of a logged operation in database 'DM_m000003_m000002_qdb', an error occurred at log record ID (116769:7548:175). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.

    Msg 3414, Level 21, State 1, Line 2

    An error occurred during recovery, preventing the database 'DM_m000003_m000002_qdb' (database ID 9) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

    Cannot do dbcc, or backup. Any tips?

  • Do you have a valid backup that does not contain the corruption?

    At minimum you need to restore the corrupt page and possibly more pages leading to the need to restore the entire backup.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Restore from backup. Don't know offhand if you can do a page restore when a DB is suspect, so may need to be a full restore. How big's the DB?

    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
  • Hi, managed to put the DB in emergency mode and do a dbcc repair.

  • What kind of repair? You may have lost data that way. Can you post the exact command?

    edit: and post output too if you saved it, from that we can tell if you lost data or not

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • sephrobbertse (8/30/2012)


    Hi, managed to put the DB in emergency mode and do a dbcc repair.

    So I assume you have no good backup, since emergency mode repair is the absolute last resort for when there is no backup and every other attempt at resolving the problem has failed.

    I strongly suggest that after you've ensured that you database is logically consistent (it probably isn't after the repair), you get a backup routine in place so that if this happens again you don't have to resort the the absolute last chance option.

    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
  • opc.three (8/30/2012)


    What kind of repair? You may have lost data that way. Can you post the exact command?

    It'll be CheckDB with REPAIR_ALLOW_DATA_LOSS as no other repair option is allowed when a DB is in emergency mode.

    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
  • GilaMonster (8/30/2012)


    opc.three (8/30/2012)


    What kind of repair? You may have lost data that way. Can you post the exact command?

    It'll be CheckDB with REPAIR_ALLOW_DATA_LOSS as no other repair option is allowed when a DB is in emergency mode.

    Ahh, I breezed right over the comment about putting it in 'emergency mode.' Thanks.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

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

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