Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server detected a logical consistency-based I/O error : SQL 2005 Expand / Collapse
Author
Message
Posted Thursday, August 30, 2012 2:24 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 12, 2013 1:06 AM
Points: 5, Visits: 15
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?
Post #1352051
Posted Thursday, August 30, 2012 9:38 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:08 PM
Points: 7,097, Visits: 12,599
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
Post #1352321
Posted Thursday, August 30, 2012 11:25 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 1:53 PM
Points: 42,771, Visits: 35,870
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 2008, MVP
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

Post #1352389
Posted Thursday, August 30, 2012 12:06 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 12, 2013 1:06 AM
Points: 5, Visits: 15
Hi, managed to put the DB in emergency mode and do a dbcc repair.
Post #1352407
Posted Thursday, August 30, 2012 12:55 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:08 PM
Points: 7,097, Visits: 12,599
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
Post #1352427
Posted Thursday, August 30, 2012 1:29 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 1:53 PM
Points: 42,771, Visits: 35,870
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 2008, MVP
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

Post #1352458
Posted Thursday, August 30, 2012 1:31 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 1:53 PM
Points: 42,771, Visits: 35,870
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 2008, MVP
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

Post #1352462
Posted Thursday, August 30, 2012 1:35 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:08 PM
Points: 7,097, Visits: 12,599
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
Post #1352465
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse