| description | MSSQLSERVER_5256 | |
|---|---|---|
| title | MSSQLSERVER_5256 | Microsoft Docs | |
| ms.custom | ||
| ms.date | 04/04/2017 | |
| ms.service | sql | |
| ms.reviewer | ||
| ms.subservice | supportability | |
| ms.topic | reference | |
| helpviewer_keywords |
|
|
| ms.assetid | 6fe254b4-2926-446f-8b20-0f1d921a4615 | |
| author | MashaMSFT | |
| ms.author | mathoma |
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 5256 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | DBCC4_INCORRECT_PAGE_ID_IN_HEADER_NO_METADATA |
| Message Text | Table error: alloc unit ID A_ID, page P_ID1 contains an incorrect page ID in its page header. The PageId in the page header = P_ID2. |
The page header of page P_ID1 contains an incorrect page ID, P_ID2.
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).