DBCC CheckDB Errors

Question

Post reply

DBCC CheckDB Errors

Viewing 4 posts - 16 through 18 (of 18 total)

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

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

Yup.

Once you've run the repair, just run checkDB with the no_infomsgs options again, to be sure it is all clean.

Have you done any root-cause analysis?

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

Paul Randal One Orange Chip Points: 29544 More actions · Answer 2

Which SP and CU of 2005 are you using? Looks like a bug has been introduced that is suppressing the repair level output when a 2570 is present - it didn't used to do that (when I wrote the code 🙂

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

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

For what it's worth Paul...

I took your DemoDataPurity database, restored it and corrupted a single page so that I'd have a checksum error as well as the data purity and it too gives no minimum repair level.

Msg 8928, Level 16, State 1, Line 1

Object ID 405576483, index ID 1, partition ID 72057594039566336, alloc unit ID 72057594044678144 (type In-row data): Page (1:3774) could not be processed. See other errors for details.

Msg 8939, Level 16, State 98, Line 1

Table error: Object ID 405576483, index ID 1, partition ID 72057594039566336, alloc unit ID 72057594044678144 (type In-row data), page (1:3774). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 63047689 and -4.

Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 405576483, index ID 1, partition ID 72057594039566336, alloc unit ID 72057594044678144 (type In-row data). Page (1:3774) was not seen in the scan although its parent (1:3898) and previous (1:3773) refer to it. Check any previous errors.

Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 405576483, index ID 1, partition ID 72057594039566336, alloc unit ID 72057594044678144 (type In-row data). Page (1:3775) is missing a reference from previous page (1:3774). Possible chain linkage problem.

CHECKDB found 0 allocation errors and 4 consistency errors in table 'Sales' (object ID 405576483).

Msg 2570, Level 16, State 3, Line 1

Page (1:24473), slot 91 in object ID 421576540, index ID 1, partition ID 72057594039697408, alloc unit ID 72057594044809216 (type "In-row data"). Column "Price" value is out of range for data type "float". Update column to a legal value.

CHECKDB found 0 allocation errors and 1 consistency errors in table 'Products' (object ID 421576540).

CHECKDB found 0 allocation errors and 5 consistency errors in database 'DemoDataPurity'.

To be honest, this is how I would personally expect it to behave. Data purity errors can't be repaired so why should there be a minimum repair level?

(asking from a logical perspective, not attacking you)

We can take this elsewhere if you like (mail, MVP mailing list, etc)

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

Kwisatz78 SSChampion Points: 12478 More actions · Answer 4

We are on 2005 RTM (I know!) - I will have to schedule some downtime to run the repair correctly.

As for root cause analysis, we don't know when it happened I am basically starting from scratch so have no event logs to correlate with. The database is now in a regular maintenance schedule.