The Database ID 30, Page (1:1141), slot 71 for LOB data type node does not exist.

Working early in the morning, I found this serious problem very depressing.

Detailed Exception:

The Database ID 30, Page (1:1141), slot 71 for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE. 

After searching a lot of articles, I finally got it done. The method is as follows:

DBCC checkdb('eshoubao')

The result is as follows:

DBCC results for 'eshoubao'.DBCC results for 'ScheduleHistory'.Msg 8961, Level 16, State 1, Line 1Table error: Object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049658880 (type LOB data). The off-row data node at page (1:1141), slot 70, text ID 6670647296 does not match its reference from page (1:1141), slot 71.Msg 8961, Level 16, State 1, Line 1Table error: Object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049658880 (type LOB data). The off-row data node at page (1:1141), slot 71, text ID 6653870080 does not match its reference from page (1:1325), slot 31.Msg 8929, Level 16, State 1, Line 1Object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049724416 (type In-row data): Errors found in off-row data with ID 6670647296 owned by data record identified by RID = (1:1325:31)There are 677 rows in 15 pages for object "ScheduleHistory".CHECKDB found 0 allocation errors and 3 consistency errors in table 'ScheduleHistory' (object ID 1749581271).CHECKDB found 0 allocation errors and 3 consistency errors in database 'eshoubao'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (eshoubao).DBCC execution completed. If DBCC printed error messages, contact your system administrator.

We can see that the table ScheduleHistory has a problem. After detailed troubleshooting, we found that the problem was recorded in February. This table has a total of over records. Thanks to these records, they are all logs and can be completely deleted.

Run the following command to fix the problem:

ALTER DATABASE eshoubaoSET single_user WITH ROLLBACK IMMEDIATE;goDBCC checkdb ('eshoubao', repair_allow_data_loss);go

Repair result:

Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.DBCC results for 'eshoubao'.DBCC results for 'ScheduleHistory'.Repair: The Clustered index successfully rebuilt for the object "dbo.ScheduleHistory" in database "eshoubao".Repair: Deleted off-row data column with ID 6670647296, for object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049658880 (type LOB data) on page (1:1141), slot 70.Repair: Deleted off-row data column with ID 6653870080, for object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049658880 (type LOB data) on page (1:1141), slot 71.Repair: Deleted record for object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049724416 (type In-row data), on page (1:1325),  slot 31. Indexes will be rebuilt.Repair: The Nonclustered index successfully rebuilt for the object "dbo.ScheduleHistory, IX_ScheduleHistory_NextStart" in database "eshoubao".Repair: The Nonclustered index successfully rebuilt for the object "dbo.ScheduleHistory, IX_ScheduleHistory_StartDate" in database "eshoubao".Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1749581271, index ID 1 will be rebuilt.        The error has been repaired.Msg 8961, Level 16, State 1, Line 1Table error: Object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049658880 (type LOB data). The off-row data node at page (1:1141), slot 70, text ID 6670647296 does not match its reference from page (1:1141), slot 71.        Could not repair this error.Msg 8961, Level 16, State 1, Line 1Table error: Object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049658880 (type LOB data). The off-row data node at page (1:1141), slot 71, text ID 6653870080 does not match its reference from page (1:1325), slot 31.        Could not repair this error.Msg 8929, Level 16, State 1, Line 1Object ID 1749581271, index ID 1, partition ID 72057594044481536, alloc unit ID 72057594049724416 (type In-row data): Errors found in off-row data with ID 6670647296 owned by data record identified by RID = (1:1325:31)        The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1749581271, index ID 2 will be rebuilt.        The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1749581271, index ID 3 will be rebuilt.        The error has been repaired.There are 696 rows in 15 pages for object "ScheduleHistory".CHECKDB found 0 allocation errors and 3 consistency errors in table 'ScheduleHistory' (object ID 1749581271).CHECKDB fixed 0 allocation errors and 1 consistency errors in table 'ScheduleHistory' (object ID 1749581271).repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (eshoubao, repair_allow_data_loss).DBCC execution completed. If DBCC printed error messages, contact your system administrator.

You will find that the problem has not been completely solved. Considering that the records in this table can be completely deleted, continue to use:

TRUNCATE TABLE ScheduleHistory

And then:

DBCC checkdb('eshoubao')

The problem has been solved:

CHECKDB found 0 allocation errors and 0 consistency errors in database 'eshoubao'.DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Finally, remember: (change the database to the multi-user mode .)

ALTER DATABASE eshoubao SET MULTI_USER WITH NO_WAIT

(Fortunately, records in this table can be deleted. If they cannot be deleted, how can we fix them? Please advise.)

This problem may occur after thinking about it:

1) Hardware problems.

2) there is a problem with the transfer (backup/restore) process.-This is the most likely because the data has been transferred several times.

　　

References:

Http://support.microsoft.com/kb/2015760

Http://www.sqlhacks.com/FAQs/DBCC-REPAIR_ALLOW_DATA_LOSS

SQL Server version: SQL server 2008 SP1

Http://www.kodyaz.com/articles/alter-single-user-multi-user-mode.aspx

Other references:

Http://www.sqlteam.com/forums/topic.asp? TOPIC_ID = 53072

Http://blogs.msdn.com/ B /psssql/archive/2008/07/15/supporting-sql-server-2008-the-system-health-session.aspx