Monday, November 30, 2009

How to Resolve “Could not read and latch...” Error Message

Data storage space in SQL database is primarily divided into numerous pages. Each page contains a 96-byte header that contains information related to page number, page type, ID, and free space. Corruption in metadata structure primarily results in failing to read the data stored on the page. This further results in making the data stored in the database inaccessible. In such situations, the data stored in the database can be accessed by restoring it from an updated backup. However, there have been instances where the backup has not been created or the backup file is corrupted due to various logical and physical factors. For accessing your database records under such circumstances, you will need to search for an advanced third-party Recover SQL application.

Consider a practical scenario, where you encounter the below error message when you attempt to mount your SQL database:

“Could not read and latch page P_ID with latch type TYPE. OPERATION failed.”

The above error message appears each time you attempt to access the database records. Furthermore, the above error message makes the database records inaccessible.


The root cause for the occurrence of the above error message is the failure of page read due to any of the below reasons:

The page is in repairing state.
An indeterminate function is being performed on the page.
The page might be read as a part of per checks of important system tables.

Note: The above scenarios can occur due to both logical and physical reasons.

To resolve the above error message and to execute your database records, you will need to
swap the damaged system component with a new one (for physical damages). For logical crash scenarios, you will need to run DBCC CHECKDB command (with correct repair clause).

Changing the damaged hardware component provides comprehensive solution to get rid of all hardware problems. But, in case of removing logical corruption scenarios, DBCC CHECKDB is not always a complete solution. For permanent resolution of all corruption scenarios, you will need to use a powerful SQL Database Repair application. Such MS SQL Repair software orderly perform database repair and recover all lost database components.

No comments:

Post a Comment