MSSQLSERVER_2531

  • Article

New: 14 April 2006

Details

Product Name

SQL Server

Product Version

9.0

Product Build Number

9.0

Event ID

2531

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

DBCC_BTREE_SIBLING_LEVEL_MISMATCH

Message Text

Table error: Object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) B-tree level mismatch, page P_ID1. Level LEVEL1 does not match level LEVEL2 from previous P_ID2.

Explanation

There are two pages linked as immediate neighbors on a level of a B-tree. The level, LEVEL2, on the right page, P_ID2, does not match the level, LEVEL1, on the left page, P_ID1.

To determine which page is incorrect, examine the surrounding pages and the contents of the two pages in question. Also, look for MSSQLEngine_8931 errors that indicate B-tree parent-child level mismatches.

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.

Warning

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 rebuild the index.