Export (0) Print
Expand All
Expand Minimize

MSSQLSERVER_2533

Product Name

SQL Server

Product Version

10.50

Product Build Number

 

Event ID

2533

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

DBCC_PAGE_WAS_NOT_SEEN

Message Text

Table error: Page P_ID allocated to object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) was not seen. Page may be invalid or have incorrect alloc unit ID in its header.

A page is allocated to the allocation unit ID, A_ID, but this allocation unit ID is not in the header of the page. The header has a different allocation unit ID. If the allocation unit ID in the header of the page is for a valid object, the page may have a matching MSSQLEngine_2534 error.

Look for Hardware Failure

Run hardware diagnostics and correct any problems. Also examine the Microsoft 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 Backup

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

Run DBCC CHECKDB

If 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 noteCaution

If you are not sure what effect DBCC CHECKDB with a REPAIR clause has on your data, contact your primary support provider before running this statement.

If running DBCC CHECKDB with one of the REPAIR clauses does not correct the problem, contact your primary support provider.

Results of Running REPAIR Options

REPAIR will deallocate the page. If the page was from an in-row data allocation unit, the index, if one exists, will be rebuilt.

Caution noteCaution

This repair may cause data loss.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft