Consistency Error

Question

Consistency Error

ps.

One Orange Chip

Points: 29423
More actions
October 9, 2010 at 9:44 am

#230218

Hi
Our weekly checkdb job failed for one of the databases. We tried running checkdb but it used to fail with this error.
Msg 8967, Level 16, State 216, Line 1
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
Then we ran dbcc checkdb with tablock option. here is the output.
DBCC results for 'TACM'.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 401971405717504 (type Unknown), page ID (1:53570) contains an incorrect page ID in its page header. The PageId in the page header = (1:938939).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 401971405717504 (type Unknown), page ID (1:53571) contains an incorrect page ID in its page header. The PageId in the page header = (1:938938).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 401971405717504 (type Unknown), page ID (1:53572) contains an incorrect page ID in its page header. The PageId in the page header = (1:938937).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 401971405717504 (type Unknown), page ID (1:53573) contains an incorrect page ID in its page header. The PageId in the page header = (1:938935).
CHECKDB found 0 allocation errors and 4 consistency errors not associated with any single object.
What caused this error? Though its a dev server and we can restore with a copy of backup from prod, I would like to know more abt this.

Pradeep Singh

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

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

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

Corruption is typically an IO subsystem problem. Look in the windows event logs, SAN logs, RAID driver logs, etc for anything out of the ordinary.

You'll have to restore. This is not a repairable error.

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

ps. One Orange Chip Points: 29423 More actions · Answer 2

Hi Gail, We had resored this db from backups. Unfortunately we didnt find any information in event logs. Since this was a dev box, even app owners too were not too keen on knowing the root-causes.

Pradeep Singh

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

ps. (10/13/2010)
Since this was a dev box, even app owners too were not too keen on knowing the root-causes.

Are they aware that without investigating and resolving root cause this could easily happen again?

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

ps. One Orange Chip Points: 29423 More actions · Answer 4

I have explained them probable consequences of this. I hope someone from the owners get hold of SAN guys to pull more information and get this fixed.

Pradeep Singh