logical consistency-based I/O error

Question

Post reply

logical consistency-based I/O error

Sushant Yadav

SSCrazy

Points: 2780
More actions
April 2, 2014 at 6:18 am

#287182

SQL Server detected a logical consistency-based I/O error:
incorrect pageid (expected 4:1738920; actual 256:10100480).
It occurred during a read of page (4:1738920)
in database ID 10 at offset 0x00000351150000 in file 'E:\xxxxxxxxxx.ndf'.
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.

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

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

Sushant Yadav SSCrazy Points: 2780 More actions · Answer 1

getting following error on

dbcc checkdb()

Msg 8909, Level 16, State 1, Line 1

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown),

page ID (4:1738920) contains an incorrect page ID in its page header.

The PageId in the page header = (256:10100480).

Msg 8998, Level 16, State 2, Line 1

Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity

checks in database ID 10 pages from (4:1738920) to (4:1747007).

See other errors for cause.

CHECKDB found 2 allocation errors and 0 consistency errors not associated with any single object.

CHECKDB found 2 allocation errors and 0 consistency errors in database

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

Sushant Yadav SSCrazy Points: 2780 More actions · Answer 3

Thanks Gila for your prompt reply,

I have restored latest backup of live database on UAT.

and it is giving me error on checkdb.

Is their any alternative solution for this.

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

Restore an earlier backup which isn't corrupt. You should know which is the latest clean backup, it'll be the one right before your scheduled checkDB started failing (you do have scheduled checkDB, right?)

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

Sushant Yadav SSCrazy Points: 2780 More actions · Answer 5

I have scheduled checkdb for the database on weekly basis.

Last run checkdb was run on last sunday and it is not showing me any error.

And I have taken last full backup on Saturday.

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

So that saturday backup should be clean, since the CheckDB which ran after it was without 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

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 7

You really need to schedule your integrity checks once a day before you do a backup. That way you know if there is corruption in the db BEFORE a backup runs.