Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

How to recover from database consistency errors?

$
0
0

I have a SQL server cluster 2005. Due to the broken of SAN storage's controller and disks, one of my SharePoint content DB has corrupted and has been causing numerous error to the SharePoint. I have run the command "DBCC CHECKDB WITH NO_INFOMDGS" and the truncated output are as following:

Table error: Object ID 53575229, index ID 1, partition ID 72057594038583296, alloc unit ID 72057594043564032 (type In-row data), page ID (3:21580503) contains an incorrect page ID in its page header. The PageId in the page header = (3:21580511).
CHECKDB found 0 allocation errors and 6 consistency errors in table 'AllDocs' (object ID 53575229).

Table error: Object ID 53575229, index ID 1, partition ID 72057594038583296, alloc unit ID 72057594043564032 (type In-row data), page ID (3:21580503) contains an incorrect page ID in its page header. The PageId in the page header = (3:21580511).
CHECKDB found 0 allocation errors and 6 consistency errors in table 'AllDocs' (object ID 53575229).

Object ID 1058102810, index ID 4, partition ID 72057594052411392, alloc unit ID 72057594058571776 (type In-row data): Page (3:21580478) could not be processed.  See other errors for details.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'EventCache' (object ID 1058102810).

Table error: Object ID 1762105318, index ID 1, partition ID 72057594055819264, alloc unit ID 72057594062897152 (type LOB data). The off-row data node at page (3:21985593), slot 35, text ID 5702751551488 is not referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1762105318, index ID 1, partition ID 72057594055819264, alloc unit ID 72057594062897152 (type LOB data). The off-row data node at page (3:21985594), slot 14, text ID 5702751354880 is not referenced.
Msg 8986, Level 16, State 1, Line 1
Too many errors found (201) for object ID 1762105318. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS".
CHECKDB found 0 allocation errors and 307 consistency errors in table 'AuditData' (object ID 1762105318).
CHECKDB found 0 allocation errors and 363 consistency errors in database 'ALCIM_WSS_Content'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WSS_Content).

Error show in the event log:

SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 3:21580475; actual 0:0). It occurred during a read of page (3:21580475) in database ID 9 at offset 0x00002929576000 in file 'E:\Microsoft SQL Server\Data\MSSQL.1\MSSQL\DATA\WSS_Content_2.ndf'. 

The last DB backup creatred was about a month ago so doing DB resotre will be my last choice. Is it possible I can recover the DB without data loss using "DBCC CHECKDB ('WSS_Content', REPAIR_REBUILD)"? Any alternative method to acheive my goal?

Thank you.


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>