| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | |
|---|---|---|---|---|---|---|---|---|---|
MSSQLSERVER_8996 |
MSSQLSERVER_8996 |
MashaMSFT |
mathoma |
04/04/2017 |
sql |
supportability |
reference |
|
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 8996 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | DBCC3_IAM_PAGE_RANGE_IN_WRONG_FILEGROUP |
| Message Text | IAM page P_ID for object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) controls pages in filegroup FG_ID1, that should be in filegroup FG_ID2. |
The index allocation map (IAM) page P_ID in filegroup FG_ID1 incorrectly includes extents from filegroup FG_ID2. All extents for an IAM page should be in the same filegroup as the IAM page itself.
Run hardware diagnostics and correct any problems. Also examine the [!INCLUDEmsCoName] Windows system and application logs and the [!INCLUDEssNoVersion] 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.
If the problem is not hardware related and a known clean backup is available, restore the database from the backup.
Not applicable. This error cannot be repaired. If you cannot restore the database from a backup, contact [!INCLUDEmsCoName] Customer Service and Support (CSS).