Table Corrupt: Object ID %d, index ID %d. Page %S_PGID not allocated or corrupt. Parent %S_PGID and previous %S_PGID refer to it.
This error means that a page is not allocated to an object that references it. When the index is used, Microsoft® SQL Server™ returns either error 605 or error 823.
Important This error is serious. Data corruption is possible.
Pages encountering error 8976 may not be included in a database backup, because database backups are performed by reading allocation pages and not by traversing page chains. Correct this error before backing up the database.
If a known clean backup is available, restore the database from the backup.
If no clean backup is available, use DBCC CHECKDB or DBCC CHECKFILEGROUP to determine the extent of the problem. Then, use DBCC CHECKDB with the appropriate repair clause to repair the damage. If the Object ID is 1 or 2 and the index ID is 1, or the table is sysfiles1, then DBCC CHECKDB cannot repair the page.
Important If either executing DBCC CHECKDB with one of the repair clauses does not correct the index problem or if you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider.
The problem can be resolved by dropping and re-creating the index in question. After the index is rebuilt, run DBCC CHECKALLOC to verify that the problem no longer exists. If it persists, call your primary support provider.
| DBCC CHECKALLOC | Errors 8000-8999 |
| DBCC CHECKDB | Reporting Errors to Your Primary Support Provider |
| DBCC CHECKFILEGROUP |