Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Corruption of sys.xml_index_nodes_85575343_32000

Author  Topic 

imarchenko
Yak Posting Veteran

57 Posts

Posted - 2008-08-21 : 18:09:59
My regular DBCC CHECKDB reported following errors:

DBCC results for 'sys.xml_index_nodes_85575343_32000'.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 213575799, index ID 1, partition ID 72057594057129984, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:1782), slot 0, text ID 638976000 is not referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 213575799, index ID 1, partition ID 72057594057129984, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:1788), slot 0, text ID 1461911552 is not referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 213575799, index ID 1, partition ID 72057594057129984, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:1791), slot 0, text ID 260046848 is not referenced.
Msg 8964, Level 16, State 1, Line 1
...
Table error: Object ID 213575799, index ID 1, partition ID 72057594057129984, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:1151005), slot 0, text ID 174194688 is not referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 213575799, index ID 1, partition ID 72057594057129984, alloc unit ID 72057594043367424 (type LOB data). The off-row data node at page (1:1151020), slot 0, text ID 876806144 is not referenced.
There are 19232 rows in 266 pages for object "sys.xml_index_nodes_85575343_32000".
CHECKDB found 0 allocation errors and 95 consistency errors in table 'sys.xml_index_nodes_85575343_32000' (object ID 213575799).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (SRWebLog.sys.xml_index_nodes_85575343_32000).
...
It appears to be an internal table. I am not sure what can be done to fix this problem. We don not have backup without DBCC errors. I am afraid the only option is to use repair_allow_data_loss.
I am not sure how critical corruption on this particular internal table and what the consequences of losing some data on this table are.

Any help is greatly appreciated.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-08-21 : 18:10:33
Moving to correct forum...

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2008-08-25 : 12:23:32
Already answered by Paul over here....

http://www.sqlservercentral.com/Forums/Topic556961-266-1.aspx


Terry
Go to Top of Page
   

- Advertisement -