June 13, 2014 at 8:26 am
We ran DBCC CHECKDB and we found some corruption in our database. What do you guys think? Correct me if I'm wrong, but does Msg 8939 tell you if there are IO issues or problems with the Hard Drive?
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 72057594039042048, alloc unit ID 72057594044743680 (type In-row data): Page (1:3535306) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 72057594039042048, alloc unit ID 72057594044743680 (type In-row data), page (1:3535306). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 130157065 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 0, partition ID 72057594039042048, alloc unit ID 72057594044743680 (type In-row data): Page (3:21038754) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 181575685, index ID 0, partition ID 72057594039042048, alloc unit ID 72057594044743680 (type In-row data), page (3:21038754). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270473 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 181575685, index ID 16, partition ID 72057594039566336, alloc unit ID 72057594045399040 (type In-row data): Page (1:3398991) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 181575685, index ID 16, partition ID 72057594039566336, alloc unit ID 72057594045399040 (type In-row data), page (1:3398991). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 16, partition ID 72057594039566336, alloc unit ID 72057594045399040 (type In-row data). Page (1:3398991) was not seen in the scan although its parent (1:4031422) and previous (1:1694525) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 181575685, index ID 16, partition ID 72057594039566336, alloc unit ID 72057594045399040 (type In-row data). Page (1:9666927) is missing a reference from previous page (1:3398991). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 8 consistency errors in table 'EDW_SFDC_HISTORY' (object ID 181575685).
CHECKDB found 0 allocation errors and 8 consistency errors in database 'SalesforceHistory'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (SalesforceHistory).
June 13, 2014 at 9:48 am
Ideally, 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
June 13, 2014 at 12:57 pm
From what I'm reading, if I run Repair with data loss, I would lose 3 pages from the database correct? What about the 8939 Msg? Should I be checking my IO? Thanks!
June 13, 2014 at 1:07 pm
Repair is not recommended, do you have a clean backup?
You have a corrupt database, therefore you need to check hardware, IO subsystem specifically. The specific errors that checkDB throws aren't what determines whether you should look at the IO subsystem or not. The presence of corruption is.
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
June 13, 2014 at 2:08 pm
Ok gotcha! Thanks for your help!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply