Topic last updated -- January 2004
Severity Level 16
Table error: Cross object linkage. Page P_ID1->next in object ID O_ID1, index ID I_ID1 refers to page P_ID2 in object ID O_ID2, index ID I_ID2 but is not in the same index.
Page P_ID is linked to page P_ID2 but the two pages are allocated to different indexes and/or objects.
Run hardware diagnostics and correct any problems. Also examine the Microsoft® Windows NT® system and application logs and the SQL Server™ error log to see if the error occurred as the result of hardware failure. Fix any hardware related problems.
If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to ensure that your system does not have write caching enabled on the disk controller. If you suspect this to be the problem, contact your hardware vendor.
Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.
RESTORE FROM BACKUP
If the problem is not hardware related and a known clean backup is available, restore the database from the backup.
If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.
Caution If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.
Repair will rebuild the index I_ID1. If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.