Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Corruption Detected Expand / Collapse
Author
Message
Posted Friday, June 13, 2014 8:26 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:12 PM
Points: 6, Visits: 131
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).
Post #1580552
Posted Friday, June 13, 2014 9:48 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:32 PM
Points: 42,458, Visits: 35,518
Ideally, restore from a clean backup.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1580593
Posted Friday, June 13, 2014 12:57 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:12 PM
Points: 6, Visits: 131
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!
Post #1580712
Posted Friday, June 13, 2014 1:07 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:32 PM
Points: 42,458, Visits: 35,518
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 2008, MVP
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

Post #1580716
Posted Friday, June 13, 2014 2:08 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:12 PM
Points: 6, Visits: 131
Ok gotcha! Thanks for your help!
Post #1580729
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse