Monday, December 7, 2009

How to Resolve “CHECKTABLE processing of object ID...” Error Message

DBCC CHECKTABLE command in SQL Server database is used to check your database table for errors. The command creates a mini dump file in the SQL Server Log Directory whenever it detects that the table is corrupt or damaged. If you wish to access the records saved in the table in such scenarios, then you will need to restore the data from an updated backup. However, if in case the backup is not available or backup falls short to restore the table records, then you will need to search for advanced SQL Server Recovery application.

As a practical case, you view the below error message in mini dump file after you run DBCC CHECKTABLE command to check your table:

“CHECKTABLE processing of object ID O_ID, index ID I_ID encountered page P_ID, slot S_ID twice. Possible internal error or allocation fault.”

Your table records become inaccessible after the above error message appears.

Cause:

The root cause for the above error message is encountering of Page P_ID during the course of scanning.

Note: Table corruption can occur either due to logical or physical damage.

Resolution:

To resolve the above error message and to access table records, you will need to follow the below steps:

Restore the data from an complete backup.
In case of physical damage, change the damaged system component.
For logical corruption scenarios, run DBCC CHECKDB using appropriate repair clause.

Swapping the damaged system component provides complete resolution from all physical damage scenarios. The other two resolution fail to perform under tow scenarios:

The backup is unavailable.
Severe Corruption of the database.

To repair your corrupted database in the above scenarios, you will need to search for an efficient SQL Database Repair tool. These MS SQL Repair applications are developed by talented data recovery experts and repair databases after almost all logically corrupted SQL databases. These repair tools use high-end scanning methods to repair and restore the recovered database components on default or user-defined destination. These read only nature of these database repair applications ensure risk-free repair of database, leaving the original database file untouched and unmodified.

No comments:

Post a Comment