|Message:||The Index Allocation Map (IAM) page P_ID1 is pointed to by the previous pointer of IAM page P_ID2 in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) but was not detected in the scan.|
An Index Allocation Map (IAM) page or metadata entry was not located, even though a reference to the page exists as the previous page link on another IAM page in an IAM chain. If the P_ID1 page is (0:0), the IAM page, P_ID2, is the start of an IAM chain, and the metadata entry for the IAM chain is missing.
Look for Hardware FailureRun hardware diagnostics and correct any problems. Also examine the Windows system and application logs and the SQL Server error log to see whether the error occurred as the result of hardware failure. Fix any hardware-related problems that are contained in the logs.If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to make sure that the system does not have write-caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor.Finally, you might find it useful to switch to a new hardware system. This switch may include reformatting the disk drives and reinstalling the operating system.Restore from BackupIf the problem is not hardware related and a known clean backup is available, restore the database from the backup.Run DBCC CHECKDBIf no clean backup is available, run DBCC CHECKDB without a REPAIR clause to determine the extent of the corruption. DBCC CHECKDB will recommend a REPAIR clause to use. Then, run DBCC CHECKDB with the appropriate REPAIR clause to repair the corruption.Caution:
Results of Running REPAIR Options
REPAIR will try to rebuild the IAM chain involving the P_ID2 page. Rebuilding the chain may involve removing pages from the chain, or removing the whole chain if the metadata is corrupted.
This repair may cause data loss.