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

Database corruption

$
0
0

Hi, 

When DBCC CheckDB was run on one of my databases, it threw the following messages. I happened to notice that this DBCC CheckDB is failed since middle of 2015 and there are no backups available.From the error messages below, it looked there is a corruption related to referencing LOB data on one single table. 


"Error="8961" Severity="16" State="1">Table error: Object ID 1371203985, index ID 1, partition ID 720 58806256533504, alloc unit ID 72057594085507072 (type LOB data). The off-row data node at page (1:11288), slot 0, text ID 2238241456586752 does not match its reference from page (1:768478), slot 18.                   
Error="8929" Severity="16" State="1">Object ID 1371203985, index ID 1, partition ID 72058806256533504, alloc unit ID 72058806489382912 (type In-row data): Errors found in off-row data with ID 267916619612160 owned by data record identified by RID = (1:768478:18)

Error="8958" Severity="10" State="1">repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (IssueDB) "

My questions are:

1) since the messages show index ID 1, could I just drop and recreate the Clustered index ? I was able to query the table without issues.

2) When sys.fn_PhysLocFormatter (%%physloc%%) is used to identify RID, it is pointing to a record in the table. I am confused whether the LOB data in the table is corrupted or LOB data in the index is corrupted?

Thanks in advance!


Viewing all articles
Browse latest Browse all 4689

Trending Articles



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