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.)

Details
Product: SQL Server
Event ID: 5228
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC4_ANTIMATTER_COLUMN_DETECTED
Message: 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 FailureRun hardware diagnostics and correct any problems. Also examine the 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 BackupIf the problem is not hardware related and a known clean backup is available, restore the database from the backup.Run DBCC CHECKDBIf 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:
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.

Related:

() An attempt to open the file “” for read / write access failed with system error : “”. The open file operation will fail with error .

Details
Product: Exchange
Event ID: 490
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>An attempt to open the file “<file name>” for read / write access failed with system error <error code>: “<error message>“. The open file operation will fail with error <error code>.
   
Explanation

An attempt to open the file [path\filename] for read/write access failed with system error [error# ]. The open file operation will fail with error [error #]. The file is either a .chk file such as E00.chk or a database file such as priv1.edb or priv1.stm. The cause depends on the error listed at the end of the Description section of the event. The most frequent causes are listed below.

  • Error -1032 = 0xfffffbf8 = 4294966264 = JET_errFileAccessDenied = Cannot access file – the file is locked or in use. Another process has “stolen” the file. A virus checker may mistakenly quarantine a file, or a backup process may temporarily deny access. A flat file backup system or antivirus software may be running against the database, check file directories, or drive M. This error can also occur if the permissions on the folder (such as MDBDATA) that contain the files for the Exchange database are not sufficient for the stores to function properly.
  • Error -1022 = 0xfffffc02 = 4294966274 = JET_errDiskIO = Disk IO error. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. Check the system log for I/O or drive errors near the time of the 490 Event. This issue can occur because the path for the check file (such as E00.chk) is not correct, which could be caused by a drive failure.
  • Error -1023 = 0xfffffc01= 4294966273 = JET_errInvalidPath = Invalid file path. This error can be caused by changing the path for the log files or the check file prior to a restore. This error can also indicate a corrupt check file (such as E00.chk) or a temporary file built during a defragmentation or a repair. In the case of the corrupt files, this error can occur even if the path to the file is correct.
   
User Action
  • For Error -1032, change the permissions on the folders that contain the Exchange store database files to the default permissions. Configure the flat file backup and antivirus software to not to scan the Exchange database subdirectories or drive M. Use Exchange-aware online backup and antivirus software.
  • For Error -1022, run “chkdsk /f /r” (without the quotation marks). If chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure. Make sure that SYSTEM has full control of Exchsrvr and all subfolders on each partition that contains Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server. Check the system log for I/O or drive errors near the time of the 490 Event. Check and correct the path for the check file (such as E00.chk). Correct the root cause and then restore from online backup if there is a recent backup or as a last resort, perform a repair, Isinteg -fix, and ExMerge to a new Exchange database.
  • For Error -1023, place the information store files back in their original locations before performing the restore. Alternatively, if the .chk is corrupt, you may be able to remove it and read all the transactions into the database. If the database remains inconsistent, then restore from online backup if there is a recent backup or as a last resort, perform a repair, Isinteg -fix, and ExMerge to a new Exchange database.

Related:

WINS found some database corruption. The record named, %1, is corrupt. It could be that recovery from the last crash did not work properly. WINS will try to recover. You may decide, however, to restore the WINS database from the backup.

Details
Product: Windows Operating System
Event ID: 4298
Source: Wins
Version: 5.0
Component: System Event Log
Symbolic Name: WINS_EVT_DATABASE_CORRUPTION
Message: WINS found some database corruption. The record named, %1, is corrupt. It could be that recovery from the last crash did not work properly. WINS will try to recover. You may decide, however, to restore the WINS database from the backup.
   
Explanation

It is possible that the recovery from the last crash did not work properly.

   
User Action

If you are concerned about the integrity of the database, restore the database from the backup.

Related:

WARNING: Because of a lazy-write error, drive %1 now contains some corrupted data. The cache is stopped.

Details
Product: Windows Operating System
Event ID: 3180
Source: System
Version: 5.0
Symbolic Name: NELOG_Lazy_Write_Err
Message: WARNING: Because of a lazy-write error, drive %1 now contains some corrupted data. The cache is stopped.
   
Explanation

This message should occur only on a workstation. Any action to correct the problem should be performed on that computer. An error occurred when the lazy-write process tried to write to the specified hard disk.

   
User Action

Run CHKDSK on the specified drive to check for problems with the disk or the files affected by the lazy-write process.

Related:

Table error: Extent P_ID in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) is beyond the range of this database.

Details
Product: SQL Server
Event ID: 2579
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC_EXTENT_OUT_OF_RANGE
Message: Table error: Extent P_ID in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) is beyond the range of this database.
   
Explanation

P_ID is a PageID of the form (filenum:pageinfile). The pageinfile of this extent is greater than the physical size of the file (filenum) of the database. The extent is marked as being allocated in an IAM page for the indicated allocation unit ID.

   
User Action

Look for Hardware FailureRun hardware diagnostics and correct any problems. Also examine the 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 BackupIf the problem is not hardware related and a known clean backup is available, restore the database from the backup.Run DBCC CHECKDBIf 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:
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 extent to be deallocated from the IAM page.

Caution:

This repair may cause data loss.

Related:

IAM page P_ID1 is pointed to by the next pointer of IAM page P_ID2 in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) but was not detected in the scan.

Details
Product: SQL Server
Event ID: 2575
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC_IAM_PAGE_WAS_NOT_SEEN
Message: IAM page P_ID1 is pointed to by the next pointer of IAM page P_ID2 in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) but was not detected in the scan.
   
Explanation

An Index Allocation Map (IAM) page was found for the specified index; however, the IAM page for its next-page pointer was not found.

   
User Action

Look for Hardware FailureRun hardware diagnostics and correct any problems. Also examine the 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 BackupIf the problem is not hardware related and a known clean backup is available, restore the database from the backup.Run DBCC CHECKDBIf 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:
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

DBCC will rebuild the index.

Related:

Table error: Page P_ID is empty in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE). This is not permitted at level LEVEL of the B-tree.

Details
Product: SQL Server
Event ID: 2574
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC_EMPTY_INDEX_TREE_LEVEL_PAGE
Message: Table error: Page P_ID is empty in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE). This is not permitted at level LEVEL of the B-tree.
   
Explanation

A B-tree page above the leaf level is empty, that is it has no rows. This behavior is possible for leaf-level pages in SQL Server 2000, but has never been possible in tree levels.

   
User Action

Look for Hardware FailureRun hardware diagnostics and correct any problems. Also examine the 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 BackupIf the problem is not hardware related and a known clean backup is available, restore the database from the backup.Run DBCC CHECKDBIf 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:
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

DBCC will rebuild the index.

Related:

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.

Details
Product: SQL Server
Event ID: 2531
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC_BTREE_SIBLING_LEVEL_MISMATCH
Message: 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.

Caution:

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.

Related:

The Index Allocation Map (IAM) page P_ID1 is pointed to by the previous pointer of IAM page P_ID2 in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) but was not detected in the scan.

Details
Product: SQL Server
Event ID: 2576
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC_IAM_PARENT_PAGE_WAS_NOT_SEEN
Message: The Index Allocation Map (IAM) page P_ID1 is pointed to by the previous pointer of IAM page P_ID2 in object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE) but was not detected in the scan.
   
Explanation

An Index Allocation Map (IAM) page or metadata entry was not located, even though a reference to the page exists as the previous page link on another IAM page in an IAM chain. If the P_ID1 page is (0:0), the IAM page, P_ID2, is the start of an IAM chain, and the metadata entry for the IAM chain is missing.

   
User Action

Look for Hardware FailureRun hardware diagnostics and correct any problems. Also examine the 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 BackupIf the problem is not hardware related and a known clean backup is available, restore the database from the backup.Run DBCC CHECKDBIf 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:
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 try to rebuild the IAM chain involving the P_ID2 page. Rebuilding the chain may involve removing pages from the chain, or removing the whole chain if the metadata is corrupted.

Caution:

This repair may cause data loss.

Related: