Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column does not exist in the partition.

Details
Product: SQL Server
Event ID: 7935
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_FS_MISSING_COLUMN
Message: Table error: Filestream directory exists for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID, but that column does not exist in the partition.
   
Explanation

During DBCC CHECKDB, a Filestream directory was found for the specified column; however, the column was not found in the corresponding metadata of the partition.

   
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

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS).

Related:

Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID was not found.

Details
Product: SQL Server
Event ID: 7934
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_FS_MISSING_ROWSET_DIRECTORY
Message: Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID was not found.
   
Explanation

During DBCC CHECKDB, a partition was found; however, its corresponding Filestream rowset directory in the Filestream dataspace was not found.

   
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

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS).

Related:

Table error: Filestream directory for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID was not found.

Details
Product: SQL Server
Event ID: 7937
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_FS_MISSING_COLUMN_DIRECTORY
Message: Table error: Filestream directory for column ID C_ID of object ID O_ID, index ID I_ID, partition ID PN_ID was not found.
   
Explanation

The specified column exists in a partition; however, its corresponding Filestream directory was not found in the Filestream dataspace.

   
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

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS).

Related:

Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID is in filegroup FG_ID1, but should be in filegroup FG_ID2.

Details
Product: SQL Server
Event ID: 7932
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_FS_ROWSET_IN_WRONG_FILEGROUP
Message: Table error: Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID is in filegroup FG_ID1, but should be in filegroup FG_ID2.
   
Explanation

During DBCC CHECKDB, the Filestream storage for an object was detected in the wrong filegroup. This could be a corruption in the metadata of the object.

   
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

Not applicable. This error cannot be repaired automatically. If you cannot restore the database from a backup, contact Microsoft Customer Service and Support (CSS).

Related:

Repair: IAM chain for object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE), has been truncated before page P_ID and will be rebuilt.

Details
Product: SQL Server
Event ID: 7915
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: DBCC2_REPAIR_IAM_CHAIN_REBUILT
Message: Repair: IAM chain for object ID O_ID, index ID I_ID, partition ID PN_ID, alloc unit ID A_ID (type TYPE), has been truncated before page P_ID and will be rebuilt.
   
Explanation

This is an information message sent by REPAIR that indicates that the specified Index Allocation Map (IAM) chain was patched so that it could be rebuilt. This patching may have required the allocation of a new head of the IAM chain or the removal of bad pages from the chain.

   
User Action

None

Related:

Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt.

Details
Product: SQL Server
Event ID: 7915
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: DBCC2_REPAIR_IAM_CHAIN_REBUILT
Message: Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt.
   
Explanation

This is an information message sent by REPAIR that indicates that the specified Index Allocation Map (IAM) chain was patched so that it could be rebuilt. This patching may have required the allocation of a new head of the IAM chain or the removal of bad pages from the chain.

Possible Causes

For explanations, see the previous errors.

   
User Action

None

Related: