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

Tuesday, February 23, 2010

Table Index Corruption May Cause SQL Server Database Corruption

Are you facing error 644 or 8646 while updating or deleting database table, which contains Unicode column with Latin1_General_BIN collation? Are you unable to access your SQL Server database? Database inaccessibility leads to critical situations of data loss and you need to restore the database from most recent backup of your database. However, if the backup is not available, you need to opt for SQL Recovery solutions to get your valuable data recovered.

In a practical scenario, you may encounter the following error in SQL Server error log while updating, deleting, or opening a database table:

“Error: 644, Severity: 21, State: 5
Could not find the index entry for RID '1613b1000000100' in index page (1:189), index ID 7, database 'TestDB'..
Error: 8646, Severity: 21, State: 1
The index entry for row ID was not found in index ID 7, of table 2009058193, in database 'test644'.”

At this point, if you run the DBCC CHECKDB statement to check the integrity and consistency of your SQL Server database, it does not report any error related to database or table index corruption discussed here. The DBCC CHECKDB tool may report you the below error message when you apply it on the problem database:

“Server: Msg 2511, Level 16, State 1, Line 1
Table error: Object ID 2009058193, Index ID 7. Keys out of order on page (1:189), slots 184 and 185.”

The above example of the error message particularly occur on the non-clustered index of MS SQL Server. But, the problem discussed here also occurs with the clustered indexes. Eventually, this behavior renders your precious data inaccessible. In order to get your database repaired and restored at this point, you must identify the cause of this problem and perform SQL Database Recovery by sorting it out.

Resolution

If you encounter the above error message after running DBCC CHECKDB tool on MDF (Master Database File), you need to rebuild indexes of the table that are indicated in error message.

On the other hand, damaged SQL Server database requires MS SQL Recovery to be handled. Recovery is best possible with the help of powerful and advanced third-party applications, known as SQL Database Recovery software.

These software are particularly designed to carry out in-depth scan of entire database and restore all of its objects such as tables, reports, forms, rules, views, triggers, and stored procedures. With read-only conduct and simple user interface, the applications are totally safe and easy to use.

Stellar Phoenix SQL Recovery is the most advanced and efficient application that provides assured recovery in all cases of MDF corruption. The software restore all MDF file objects from Microsoft SQL Server 2008, 2005, and 2000.

SQL Database Recovery Related Articles :-
http://filerepairtools.weebly.com/sql-recovery-software.html
http://sqlrecoverydatabase.blogspot.com/2009/12/resolving-forward-row-mismatch-error.html
http://sqlrecoverydatabase.blogspot.com/2009/12/database-suspect-due-to-problems-while.html
http://www.jamespot.com/a/716091-Damaged-SQLServerAgent-Service-Might-Cause-MDF-Corruption.html

Wednesday, February 17, 2010

How to Fix Master Database Corruption in MS SQL Server

In Microsoft SQL Server, all the system-level data/information are stored in a Master database. It includes the instance-wide meta data like logon accounts, linked servers, system configuration settings, and endpoints. Furthermore, master database records the creation of other database and location of the database files and initialization information for MS SQL Server. Thus, Microsoft SQL Server can't start if master database is missing, damaged, or unavailable. Corruption of the master database leads to critical data loss situations and requires SQL Recovery.

Microsoft SQL Server facilitate checking the integrity, both logical and physical, of all objects in specified database through DBCC CHECKDB. It includes three modules- DBCC CHECKALLOC, DBCC CHECKTABLE, and DBCC CHECKCATALOG, which are used to perform specific operations. If you run DBCC CHECKDB on any database, you need not run any of its modules on the affected SQL Server database. It also validates contents of indexed view, link-level consistency among file system files/directories and table meta data, and Service Broker data in SQL database.

However, the DBCC CHECKDB can not handle database corruption in all cases and thus your master database may remain inaccessible in those cases. The problem generally occurs in case of severe corruption to the database. In a practical scenario, you may come across the below error message when you run DBCC CHECKTABLE module on a corrupt master database:

“Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'master', index 'syscolumns.ncsyscolumns' (ID 3) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:425:11) with values (id = 1794105432 and name = 'COLUMN_NAME' and number = 0 and id = 1794105432 and colid = 4 and number = 0)
points to the data row identified by ().
CHECKTABLE found 0 allocation errors and 1 consistency errors in table 'syscolumns' (object ID 3).
repair_fast is the minimum repair level for the errors found by DBCC CHECKTABLE (master.dbo.syscolumns ).”

In such situations, you need to use third-party SQL Database Recovery application to get your database repaired and restored. The MS SQL Recovery applications come equipped with self-descriptive and rich graphical user interface to provide easy and quick SQL Server Recovery. The applications have read-only conduct to provide safe recovery.

Stellar Phoenix MSSQL Database Recovery is a powerful application to restore tables, defaults, triggers, stored procedures, rules, and views from damaged MS SQL Server database. The software works well with all database, created through MS SQL Server 2008, 2005, and 2000.

Tuesday, February 16, 2010

File Header and Boot Page corrupted in MS SQL Server Database

Just like any other database, MS SQL Server database contains a file header page and boot page. While the file header page (8KB) consists of metadata information about the database, the boot page contains critical information about the database itself. Corruption in any of the above pages primarily results in an error message that result in unmounting of the SQL database. This further results in the inaccessibility of SQL database records, used for various personal and professional uses. In such cases, an ideal way to resolve the above error message is by restoring data from an updated backup. But with inaccessibility of database backup, the only option to access your records is by using an advanced SQL Recovery application.

Consider a practical case, where either of the below error messages pops up when you attempt to access your SQL Server database:

“Msg 5172, Level 16, State 15, Line 1
The header for file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\FileHeaderTest.mdf' is not a valid database file header. The PageAudit property is incorrect.”
Or
“Msg 913, Level 16, State 4, Line 1
Could not find database ID 19. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.”

The first error message is caused due to corruption of file header page and the second is a result of boot page corruption. The database records become inaccessible after any of the above error message pops up.

Cause:
Corruption in boot page or file header is due to improper system shutdown, application malfunction, etc. In both the above cases of corruption, repair is not possible by running DBCC CHECKDB command.

Resolution:

To resolve the above error messages and to systematically access the database records, you need to use an efficient third-party SQL Database Recovery application. A SQL Repair tool employs high-end scanning procedures to repair corrupt SQL database and restore it at required destination.

SQL Recovery is a powerful, yet easy to use SQL Repair application that allows even a non-technical user to perform database repair. The read only software is competent enough to repair database built with MS SQL Server 2008, 2005, and 2000. It supports Windows 7, Vista, 2008, XP, 2003, and 2000.

Source Taken From :- http://www.articlesengine.com/Article/File-Header-and-Boot-Page-corrupted-in-MS-SQL-Server-Database/505733/1

Wednesday, February 10, 2010

Resolving “Extent E_ID in database” Error Message

The records saved in a SQL Server database table is divided into various pages, such as GAM (Global Allocation Map) , SGAM (Secondary Global Allocation Map), and IAM (Index Allocation Map). A GAM page comprises of one bit per extent for all the mapped extents in a file interval. An SGAM page is exactly similar to GAM page, the only difference being that every set bit is equal to an extent, in which these pages are individually assigned to IAM pages. An IAM page consists of one bit per dedicated extent. The values saved in the Extents can be get corrupted, if there is any logical corruption in the SQL database. In such scenarios, the database records saved in the tables become inaccessible. Furthermore, you also receive an error message while opening the table. In such cases, the database records saved in the table can be accessed by restoring the table from an up-to-date backup. But, in case of backup unavailability, you will need to opt for powerful SQL Database Recovery utility.

Consider a practical situation, where you receive the below error message while opening a SQL table:

“Extent E_ID in database ID DB_ID is allocated in both GAM GAM_P_ID and SGAM SGAM_P_ID.”

The above error message makes the table records inaccessible.

Cause:

The above error message occurs under following circumstances:

Extent is mixed and dedicated.
Extent is unallocated and dedicated.
Extent is unallocated, mixed, and dedicated.
Extent is unallocated and mixed.

Resolution:

The resolution for the above error message (either due to logical or physical corruption) is discussed below:

Table corrupted due to physical damage required changing of physically damaged component. To identify the damaged component, check the SQL Server and operating system logs.
Table corruption, if occurred due to logical crash, requires you to run DBCC CHECKDB statement without the repair clause. This step enable you identify the exact extent of corruption. Then you will need to search for exact repair clause and run with DBCC CHECKDB command. However, if the error message sustains even after running the above command, then you will need to use advanced SQL Recovery utility. Such SQL Repair tools are readily available on the Internet.

SQL Recovery is one of the finest SQL Database Repair application that repairs SQL Server 2008, 20005, and 2000 database tables and other database components. It is designed for Windows 7, Vista, 2008, XP, 2003, and 2000 operating systems.

Resource Taken From :- http://www.articlesengine.com/Article/Resolving--Extent-E-ID-in-database--Error-Message/499897/1

Tuesday, February 9, 2010

Fixing “Table error: Cross object linkage...” Error Message

Pages in metadata structure of MS SQL Server database are either linked in a B-tree or heap tree format. These pages contain the records of different database components. In such situations, these pages instead of pointing the required pages, start pointing to a wrong page. The database records become inaccessible in case the SQL database gets corrupted or damaged. To access the records saved in the database components, an easy way is to restore the database objects from an updated backup. But, if in case the backup is not available, or backup file is not created, then you will need to repair the SQL database to access all its records. To do so, you will need to use advanced third-party SQL Recovery utility.

To briefly explain the above database corruption scenario, below is the error message that pops up when a SQL database table gets corrupted:

“Table error: Cross object linkage: Parent page P_ID1, slot S_ID1 in object ID O_ID1, index ID I_ID1, and page P_ID2, slot S_ID2 in object ID O_ID2, index ID I_ID2, next refer to page P_ID3 but are not in the same object.”

The above error message makes the data saved in the database table inaccessible. In additions, the user can not perform any operations, such as, addition, modifications, or deletion, on the records of that table. It is a severity level 16 error message.

Cause:

The above error message occurs when the page P_ID2 and page P_ID1's child page pointer in a B-tree, point to the page P_ID3 in some other object. This can happen either due to logical or physical corruption of SQL database.

Resolution:
To isolate the above error message and access the database table records, you will need to follow the below steps:
To isolate the error message, if caused due to physical corruption, change the damaged system component with a new component.
For error message caused due to logical damage, use the DBCC CHECKDB command with appropriate repair clause. But, if the problem sustains, then use SQL Database Repair software to repair the database. Such SQL Database Recovery utilities repair the database components by incorporating effective scanning algorithms.

Stellar Phoenix SQL Recovery is a repair utility that provides orderly repair of SQL Server 2008, 20005, and 2000 database components. The repairable components can be previewed and restored at user-specified location. The SQL Repair tool works on Windows 7, Vista, 2008, XP, 2003, and 2000 operating systems.

Resource Taken From :-
http://www.articlesengine.com/Article/Fixing--Table-error--Cross-object-linkage-----Error-Message/499304/1

Friday, February 5, 2010

Tips to resolve “Table error … offset 0xADDRESS is invalid” Error

A table in MS SQL database can be corrupted due to various reasons. One of the most common being the corruption in metadata structure, caused due to damage of SQL Server damage. Once the table gets corrupted, it fails to display records stored in it. Furthermore, you also receive an “Table Error” message that does not allow you add any new records. An easy way to overcome such hazards is by restoring the table from an updated backup. But, with probabilities of backup file being corrupted, not updated, or inaccessible always exist. In such situations, the database user is left with no option, but to repair the corrupted table. To effectively do so, the user need to search for an advanced SQL Recovery application.

To illustrate the above case, below is a Table error message that appears after your SQL database table gets corrupted:

“Table error: Object ID O_ID, index ID I_ID, page P_ID. Test (TEST) failed. Slot S_ID, offset 0xADDRESS is invalid.”

The consequences of this error message might prove fatal, as it makes all the records inaccessible.

Cause:

The above Table error message pops up after the table gets corrupted due to logical or physical crash.

Resolution:

The resolution for the above Table error message is discussed below:

In case the table is corrupted due to hardware (system component) crash, then the database user needs to check the logs of SQL Server and System. This enables the user to verify the component that is physically damaged. For comprehensive resolution, the user needs to install a new component in place of damaged component.
In case the table is corrupted due to logical crash, then the user needs to run DBCC CHECKDB with a repair clause. In most cases, the above command repairs the database tables. But if in case, the above falls short of repairing the damaged table, then the user needs to look out for an effective SQL Repair application.

A SQL Repair software is a product developed by highly qualified database repair experts. The tool is easily understood without any prior technical knowledge.

SQL Recovery is an absolute answer to all SQL database corruption scenarios. The software repairs all database file components created in SQL Server 2008, 20005, and 2000. Designed for Windows 7, Vista, 2008, XP, 2003, 2000, the SQL Repair utility is totally non-destructive.

Resource Taken From :-
http://www.articleblast.com/Computers_and_Internet/Programming/Tips_to_resolve_%22Table_error_%85_offset_0xADDRESS_is_invalid%22_Error/

Wednesday, February 3, 2010

Fixing “Table Error ... index ID I_ID B-tree level mismatch...” Error


Corruption of MS SQL database can result into damage of metadata structure entries, which can further result into inaccessibility of records saved in the SQL database components. In most cases of metadata structure damage, you receive an error message that specifies the exact metadata entry, which is corrupt. To overcome the error message and to access the database components records, an ideal way is to restore it from an updated backup. However, there are thousand of situations, where either the backup gets corrupted or the database administrator forgets to create a backup. In such cases, the only way to access records of a corrupted SQL database component is by repairing it with a powerful third-party MS Recover SQL application.

Consider a practical case, where you receive the below error message while trying to access a SQL database table:

“Table error: Object ID O_ID, index ID I_ID B-tree level mismatch, page P_ID1. Level LEVEL1 does not match level LEVEL2 from parent P_ID2.”

The table error message doe not allows the table to open, resulting into inaccessibility of all its records.

Cause:

The cause for the above table error message is metadata structure damage, due to which the values of the pages (stored in the form of B-tree structure) changes. The changed values corrupt the linking between the parent nodes and the child nodes in a B-tree.

Resolution:

To resolve SQL database corruption, caused due to any reason, follow the below measures:

If the corruption in SQL database is caused due any physical damage of the system component, then you will need to swap that component with a new component.
If the problem persists even after changing the system component, then it is a logical corruption scenario. For such cases, you will need to run DBCC CHECKDB command with a repair clause.

However, if the error message appears even after running the command, then you will need to opt for a effective SQL Repair utility that can repair your database. The demo versions of such MS SQL Recovery tools allows you to preview you repaired SQL database.

Resource Taken From :- http://www.articlesengine.com/Article/Fixing--Table-Error-----index-ID-I-ID-B-tree-level-mismatch-----Error/494646/1