Wednesday, February 24, 2010

Fixing “FirstIAM field in sysindexes is P_ID. FirstIAM for...” Error

A FirstIAM field in MS SQL Server database is the destination of first IAM (Index Allocation Map) page for the index. An IAM page acts like an allocation structure which SQL Server uses to track database objects. The FirstIAM page consists of a value that changes when dummy indexes do not contain the exact storage allocated to them. This primarily occurs when your SQL Server database gets corrupted due to logical or physical reasons. Furthermore, you also receive an error message after the value of FirstIAM page changes. This error message makes the data saved in the SQL database components inaccessible. To overcome the error message in such cases, follow the straight forward approach of restoring the data from an updated backup. However, if the database backup is inaccessible or corrupt/damaged, then use an advanced SQL Recovery application.

To thoroughly explain the above case, below is the error message with its detailed description:

“Object ID O_ID, index ID I_ID: FirstIAM field in sysindexes is P_ID. FirstIAM for statistics only and dummy index entries should be (0:0).”

The above error message appears when the dummy index(es) contain incorrect storage. As a result, the value for FirstIAM page should be 'zero'. However, in this case, the value for FirstIAM page is not 'zero'. After the above error message pops up, the SQL Server database records become inaccessible.

Resolution:

The resolution for the above error message can only be achieved by repairing the database. To do so, you will need to follow the below steps:

If the database is damaged due to any physical damage of a system component, then you will need to change the damaged component with a new component.
If the SQL Server database is logically corrupted, then you will need to execute DBCC CHECKDB command with a suitable repair clause. In most cases, the database is repaired after you run the above command. However, if the command does not repairs your corrupt database, then you will need to use advanced SQL Database Recovery application. The SQL Repair tools use powerful repairing algorithms to repair any logically corrupted database.

SQL Recovery repairs logically corrupt databases and restores them on your desired destination. In addition, the SQL Repair software does not makes even a single change in the original database records. It is compatible with SQL Server 2008, 20005, and 2000 and designed for Windows 7, Vista, 2008, XP, 2003, 2000.

SQL Recovery Related Articles :-
http://www.thefreelibrary.com/Applying+CHECKDB+on+Tempdb+Cause+Data+Loss-a01073994023
http://www.jamespot.com/a/723798-How-to-Resolve-Extent-E-ID-in-Database-ID-Error-Message.html

No comments:

Post a Comment