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

Question

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

charipg

SSCrazy Eights

Points: 9888
More actions
June 6, 2012 at 7:04 am

#275205

I Checked the database in MS Query Analyser. I am getting the following error when trying to sort a column in the 'table1' in 'proddb' database o
"SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:263786; actual 50:3342385). It occurred during a read of page (1:263786) in database ID 6 at offset 0x00000080cd4000 in the file "H:\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\proddb.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"
I ran dbcc checkdb then getting the below error:
Msg 8967, Level 16, State 216, Line 1
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
DBCC results for 'proddb'.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'proddb'.
can anyone suggest to resolve this ..

Viewing 12 posts - 1 through 11 (of 11 total)

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

Perry Whittle SSC Guru Points: 234013 More actions · Answer 1

charipg (6/6/2012)
I Checked the database in MS Query Analyser. I am getting the following error when trying to sort a column in the 'table1' in 'proddb' database o
"SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:263786; actual 50:3342385). It occurred during a read of page (1:263786) in database ID 6 at offset 0x00000080cd4000 in the file "H:\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\proddb.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"
I ran dbcc checkdb then getting the below error:
Msg 8967, Level 16, State 216, Line 1
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
DBCC results for 'proddb'.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'proddb'.
can anyone suggest to resolve this ..

Do you have a backup of this database?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

Restore from a clean backup

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

Geoff A SSChampion Points: 11511 More actions · Answer 3

I'm really curious as to HOW a dbcc checkdb runs cleans whilst a select query returns the I/O error...

if that is possible, then how would one know when the last clean backup was taken???

Gail, any thoughts?

o wait, is this the clue

An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

Geoff A (6/6/2012)
I'm really curious as to HOW a dbcc checkdb runs cleans whilst a select query returns the I/O error...

CheckDB didn't run clean. It didn't run at all.

Msg 8967, Level 16, State 216, Line 1
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.

Whatever's wrong, it's bad enough that CheckDB can't run, so there is no way this will be repairable.

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

charipg SSCrazy Eights Points: 9888 More actions · Answer 5

is DBCC CHECKDB REPAIR_REBUILD works for this issue ?

Geoff A SSChampion Points: 11511 More actions · Answer 6

charipg (6/6/2012)
is DBCC CHECKDB REPAIR_REBUILD works for this issue ?

i wouldn't do that in PROD. you could run that command in a lower enviroment and TEST, TEST, TEST.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

charipg (6/6/2012)
is DBCC CHECKDB REPAIR_REBUILD works for this issue ?

No, it won't do a thing because CheckDB couldn't run successfully to check the DB so there's no chance at all it's going to be able to repair the damage if it can't even figure out what the damage is.

Restore from a clean backup. If your backup strategy is up to spec and your integrity checks are being done correctly, you should be able to restore without any data loss.

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

charipg SSCrazy Eights Points: 9888 More actions · Answer 8

can i stop dbcc checkdb repair_rebuild command ?

is there any problem if i stop?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 9

You can stop it at any time.

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

Perry Whittle SSC Guru Points: 234013 More actions · Answer 10

charipg (6/6/2012)
is there any problem if i stop?

it's hosed already so it won't make an ounce of difference 😉

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Jo Pattyn SSC-Dedicated Points: 32348 More actions · Answer 11

if it is an index, you could try to drop it and rebuild