Topic last updated -- January 2004
Severity Level 16
Table error: Object ID O_ID, index ID I_ID, page ID P_ID1. The PageId in the page header = P_ID2.
DBCC asked for page P_ID1. When the page was read from disk, the page ID in its header was found to be P_ID2.
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.
The result of a repair depends on the page type.
- PFS page: No repair possible.
- Allocation page: The page is reformatted and rebuilt.
- Other pages: The page is de-allocated.
If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.