I understand that looking at
DBCC PAGE is supposed to show me the last known good
DBCC CHECKDB but I am not seeing this work correctly.
I have a database that I know is corrupted. If I run
DBCC CHECKDB the errors are displayed as expected (see below).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'Blah' (object ID 251147940). Msg 2508, Level 16, State 3, Line 1
When I run the below to evaluate
dbi_dbccLastKnownGood, I get the time that the
CHECKDB was just run down to the second.
DBCC PAGE ('Blah', 1, 9, 3) WITH TABLERESULTS;
I've read Paul Randal's information, and from that, it looks like I'm doing/reading this correctly. Has anyone seen this before and if so, any thoughts on working around it?
Here is a complete sample of the error. I am getting 12 of these for different tables.
Msg 2508, Level 16, State 3, Line 1 The In-row data RSVD page count for object "Mailings", index ID 0, partition ID 16459231395840, alloc unit ID 16459231395840 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE. CHECKDB found 0 allocation errors and 1 consistency errors in table Mailings' (object ID 251147940).