MSSQLSERVER_5228

Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

Details

Product Name

SQL Server

Event ID

5228

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

DBCC4_ANTIMATTER_COLUMN_DETECTED

Message Text

Table error: Object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE), page PG_ID, row R_ID. DBCC detected incomplete cleanup from an online index build operation. (Antimatter column value is VALUE.)

Explanation

An unfinished online index build was detected for object O_ID, index I_ID, and partition PN_ID. This is manifested by the presence of an antimatter column on the row R_ID. An antimatter column is used when reconciling records from multiple sources during an online index build. The error message also indicates the value of the antimatter column.

User Action

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

Running REPAIR will cause the specified index and all its dependent indexes to be rebuilt.

See Also

Reference

DBCC CHECKDB (Transact-SQL)