In SQL Server storage space is divided into pages, numbered sequentially. Each database page has a type that defines the type of data that is contained in the page, for example an index page or a data page. If any of these pages gets corrupt, SQL Server reports errors. You can detect this corruption by running DBCC CHECKDB command. However, to recover from such data loss, you will need to use your backup to restore. But if no clean backup is available at the moment, you should use SQL Recovery software.
At times, when you run DBCC command to check the consistency of your SQL Server database, you might come across the below error :
“Msg 2503, Level 16, State 1 Table Corrupt: Page linkage is not consistent; check the following pages: current page#=xxx; page# pointing to this page=yyyy; previous page#=zzzz”
Cause
Error 2503 might be encountered due to any of the possible reasons:
You are not running DBCC in single-user mode and some updates are running
Table data page or index page is corrupt
Solution
To solve the problem, discussed above, you need to apply these methods:
Make sure that you run DBCC in single-user mode
If you are using the command in single-user mode, you need to check for a valid data backup to restore the lost data
If you don't have any good data backup, use DBCC PAGE command to find out whether the infected page is a data page or an index page
To fix index corruption, you should drop and then recreate the index of the table
You need to copy all the database objects and data to a new database if the data pages are affected. You might fail to copy corrupted tables. Drop the old database
If applying the above measures doesn't help, you should use third-party SQL Repair utility to safely repair and restore the damaged database and its objects. SQL Recovery software apply powerful scanning algorithms and retreive data while maintaining their intactness.
Stellar Phoenix SQL Recovery is an advanced utility to repair damaged SQL databases. It supports SQL Server 2008, 2005 and 2000. With self-descriptive and exceptionally realistic interface, advanced repair options and non-destructive design, it is an effective SQL Repair tool to repair all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
Wednesday, August 26, 2009
Monday, August 24, 2009
How to Troubleshoot SQL Server Error 8910?
An SQL Server database is divided into pages each of 8 KB in size. An IAM (Index Allocation Map) page is the one that holds information about table extents or index information for each allocation unit. The page contains the location information of first 8 pages and also bitmap of extents for used extents. These are mixed pages but do not reference themselves. Among other things, an IAM page contains a mixed page array, which is actually an array of eight page IDs that holds mixed pages that have been allocated to the index. An SQL Server database might sometimes report corruption errors in these IAM pages. To restore lost information in such way, you will need to either use your recent database backup or use SQL Recovery tools to scan and repair the corrupted database.
For an example, you might come across the below error with your SQL Server database
“Server: Msg 8910, Level 16, State ST_NO Line L_NO
Page P_ID in database ID DB_ID is allocated to both object ID O_ID1, index ID I_ID1, and object ID O_ID2, index ID I_ID2.”
Where, ST_NO is the state of error message and can be either '1' or '2'.
Cause
If you receive the above error with state '1', this implies there exist two indexes that have their page allocated in either of mixed page array of IAM page. However, if you are getting this error with state '2' the reason could be that there exists a page that has been entered twice in mixed page array of an IAM page. These typically represent database in inconsistent state.
Solution
Follow these measures to solve the given problem:
Restore from backup if available and exists in valid state for complete restoration
Execute DBCC CHECKDB. Doing so will let your know the exact repair clause that should be applied to repair the database. Again, run DBCC CHECKDB with this clause.
Applying the above step might cause some data to be deleted. To prevent this, use safe SQL Repair tools that are competent to repair corrupted SQL Server database in any set of conditions. SQL Recovery software provide easy repair options through interactive interface and comprehensive recovery results.
SQL Recovery is an advanced SQL Server Recovery tool for damaged SQL Server databases. It supports repair for SQL Server 2008, 2005 and 2000. The software is available with self-descriptive interface and restores all database objects including tables, user defined data types and functions, triggers, stored procedures, views, rules etc. The software is compatible with Windows Vista, XP, 2003, 2000, and NT.
For an example, you might come across the below error with your SQL Server database
“Server: Msg 8910, Level 16, State ST_NO Line L_NO
Page P_ID in database ID DB_ID is allocated to both object ID O_ID1, index ID I_ID1, and object ID O_ID2, index ID I_ID2.”
Where, ST_NO is the state of error message and can be either '1' or '2'.
Cause
If you receive the above error with state '1', this implies there exist two indexes that have their page allocated in either of mixed page array of IAM page. However, if you are getting this error with state '2' the reason could be that there exists a page that has been entered twice in mixed page array of an IAM page. These typically represent database in inconsistent state.
Solution
Follow these measures to solve the given problem:
Restore from backup if available and exists in valid state for complete restoration
Execute DBCC CHECKDB. Doing so will let your know the exact repair clause that should be applied to repair the database. Again, run DBCC CHECKDB with this clause.
Applying the above step might cause some data to be deleted. To prevent this, use safe SQL Repair tools that are competent to repair corrupted SQL Server database in any set of conditions. SQL Recovery software provide easy repair options through interactive interface and comprehensive recovery results.
SQL Recovery is an advanced SQL Server Recovery tool for damaged SQL Server databases. It supports repair for SQL Server 2008, 2005 and 2000. The software is available with self-descriptive interface and restores all database objects including tables, user defined data types and functions, triggers, stored procedures, views, rules etc. The software is compatible with Windows Vista, XP, 2003, 2000, and NT.
Thursday, August 20, 2009
Resolving SQL Table Error: Cross Object Linkage
SQL Server uses index information so that if you process a query that could fetch quick results. These are created on table columns. An index is basically comprised of various pages, arranged in the form of a B-tree structure. So, as you execute a query, the engine starts navigating from the root node and continue through the intermediate nodes till the leaf node is reached. Any malfunction in this index structure might introduce table corruption errors. Such situations require you to restore the data from backup or use SQL Repair utilities that could repair the database and its components effectively.
You might encounter the below table error with your SQL Server database:
“Table error: Cross object linkage. Page P_ID1->next in object ID O_ID1, index ID I_ID1 refers to page P_ID2 in object ID O_ID2, index ID I_ID2 but is not in the same index.”
This error is marked as error 8982 in SQL Server error log with severity level 16.
Cause
An SQL Server table results the above error if the two pages (P_ID1 and P_ID2) have been marked with dissimilar index and/or object information though they have been marked as linked.
Note: If you observe these problems persistently occurring, the possible reason is hardware malfunction.
Solution
Such table corruption errors should be resolved by following these methods:
First, you need to analyze your system for possible hardware problems. You can deduce such problems through error logs of operating system, application and SQL Server™ . Try to fix such problems, if any.
If you have valid data backup available, you need to restore your lost data from it.
If issue persists because of unavailability of clean data backup, you can run DBCC CHECKDB command that will let you know the exact repair clause that could fix this corruption. Execute DBCC CHECKDB command using the recommended repair clause.
Applying the above measure can cause data loss. Thus, for better and safe SQL Recovery, you should use third-party tools to scrutinize and repair damaged SQL Server databases. SQL Repair applications are built with powerful technology to assist database recovery in each possible case of corruption.
SQL Recovery is a comprehensive tool to repair damaged SQL databases for SQL Server 2008, 2005 and 2000. With self-descriptive interface, advanced repair options and read-only design, it is an effective SQL Repair tool to repair and restore all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
You might encounter the below table error with your SQL Server database:
“Table error: Cross object linkage. Page P_ID1->next in object ID O_ID1, index ID I_ID1 refers to page P_ID2 in object ID O_ID2, index ID I_ID2 but is not in the same index.”
This error is marked as error 8982 in SQL Server error log with severity level 16.
Cause
An SQL Server table results the above error if the two pages (P_ID1 and P_ID2) have been marked with dissimilar index and/or object information though they have been marked as linked.
Note: If you observe these problems persistently occurring, the possible reason is hardware malfunction.
Solution
Such table corruption errors should be resolved by following these methods:
First, you need to analyze your system for possible hardware problems. You can deduce such problems through error logs of operating system, application and SQL Server™ . Try to fix such problems, if any.
If you have valid data backup available, you need to restore your lost data from it.
If issue persists because of unavailability of clean data backup, you can run DBCC CHECKDB command that will let you know the exact repair clause that could fix this corruption. Execute DBCC CHECKDB command using the recommended repair clause.
Applying the above measure can cause data loss. Thus, for better and safe SQL Recovery, you should use third-party tools to scrutinize and repair damaged SQL Server databases. SQL Repair applications are built with powerful technology to assist database recovery in each possible case of corruption.
SQL Recovery is a comprehensive tool to repair damaged SQL databases for SQL Server 2008, 2005 and 2000. With self-descriptive interface, advanced repair options and read-only design, it is an effective SQL Repair tool to repair and restore all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
Tuesday, August 18, 2009
Resolving SQL Server Error 8942
A SQL Server database table is prone to corruption due to unexpected shutdown, application errors, hardware bugs and similar other faults, thereby resulting into DBCC CHECKDB errors or inaccessible table. To resolve such issues, it becomes essential that you restore from the latest database backup. But sometimes, it is not feasible to restore complete information from the backup. Thus, you should use SQL recovery tools to repair these databases.
As an instance, you might encounter the below error with SQL Server table:
Server: Msg 8942, Level 16, State 1
Table error: Object ID O_ID, index ID I_ID, page P_ID. Test (TEST) failed. Slot S_ID, offset 0xADDRESS overlaps with the prior row.
Cause
The above error occurs due to overlapping of slots. It primarily occurs when the offset of slot S_ID is not equal or greater to previous slot end. The error is the result of a table test, in which sorted[i].offset has not been found greater or equal to a expected value, 'max'. Here, 'max' signifies the end of last slot and [i] is the ADDRESS.
Solution
To troubleshoot these database table errors, you are recommended to consider these methods:
If you are encountering such problems repeatedly, it might be due to hardware issues. So, you need to diagnose the system, application and SQL Server™ error log to know the exact hardware issues, if any. Remove, swap and replace the damaged hardware
If this is not a known hardware problem, restore the database from the recent data backup
In cases, when you don't have any valid data backup, you need to run DBCC CHECKDB command without using any repair clause. This will allow you to determine the exact repair clause required to be applied for database repair. Next, run DBCC CHECKDB with this repair clause.
Applying the above measure can cause data loss. To perform safe database repair, you should use SQL Repair software. These are perfect tools that apply safe scanning algorithms to result effective repair of complete database and its components. SQL Recovery tools are highly competent utilities with graphically rich user interface.
Stellar Phoenix SQL Recovery is a comprehensive SQL Repair utility to repair damaged databases created with SQL Server 2008, 2005 and 2000. It is a fully-competent tool that restores all database components including triggers, stored procedures, views, rules and more. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
As an instance, you might encounter the below error with SQL Server table:
Server: Msg 8942, Level 16, State 1
Table error: Object ID O_ID, index ID I_ID, page P_ID. Test (TEST) failed. Slot S_ID, offset 0xADDRESS overlaps with the prior row.
Cause
The above error occurs due to overlapping of slots. It primarily occurs when the offset of slot S_ID is not equal or greater to previous slot end. The error is the result of a table test, in which sorted[i].offset has not been found greater or equal to a expected value, 'max'. Here, 'max' signifies the end of last slot and [i] is the ADDRESS.
Solution
To troubleshoot these database table errors, you are recommended to consider these methods:
If you are encountering such problems repeatedly, it might be due to hardware issues. So, you need to diagnose the system, application and SQL Server™ error log to know the exact hardware issues, if any. Remove, swap and replace the damaged hardware
If this is not a known hardware problem, restore the database from the recent data backup
In cases, when you don't have any valid data backup, you need to run DBCC CHECKDB command without using any repair clause. This will allow you to determine the exact repair clause required to be applied for database repair. Next, run DBCC CHECKDB with this repair clause.
Applying the above measure can cause data loss. To perform safe database repair, you should use SQL Repair software. These are perfect tools that apply safe scanning algorithms to result effective repair of complete database and its components. SQL Recovery tools are highly competent utilities with graphically rich user interface.
Stellar Phoenix SQL Recovery is a comprehensive SQL Repair utility to repair damaged databases created with SQL Server 2008, 2005 and 2000. It is a fully-competent tool that restores all database components including triggers, stored procedures, views, rules and more. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
Monday, August 17, 2009
Resolving SQL Page with Incorrect Type Error
All the SQL database files are split into PFS intervals, where PFS stands for Page Free Space. A PFS interval is about 64 MB in size and has 8088 pages in it. Each PFS page has a byte-map with one byte per page for all the pages included in the PFS interval. At times, you get database errors that indicate that a page exists with invalid type in its PFS page. Database corrupted in this way needs to be restored from backup. However, if you don't have any valid data backup available, you need to use advanced SQL Recovery application.
For an instance, you might come across the similar error message with your SQL Server database:
“Database error: Page P_ID1 is marked with the wrong type in PFS page P_ID2. PFS status 0xVAL1 expected 0xVAL2.”
This error is marked as error 8948 in SQL Server error log.
Cause
The above error results when a page P_ID1 has been marked with incorrect type entry in PFS page P_ID2. As described above, each PFS page has a byte-map with one byte per page for all the pages included in the PFS interval. Among rest of the information, each byte contains three specific type of status bits that define the page type:
(0x10) for PFS_IS_IAM_PG
(0x40) for PFS_IS_ALLOCATED
(0x20)for PFS_IS_MIXED_EXT
Error 8948 occurs when these bits are improperly set.
Solution
You need to deploy these measures to cope up with such issues:
If such kind of problems are persistent in nature, you should check the system for possible hardware problems first. You can do so by examining the error log reports of Windows, SQL Server™ and application.
Check the database backup status. If complete and valid, delete the damaged database and restore from the backup.
Without using any repair clause, execute DBCC CHECKDB to determine the required repair clause to be applied. Next, run DBCC CHECKDB with this repair clause.
If you desire to prevent data loss that might occur due to the above step, you need to use advanced SQL Repair tools. These are safe SQL Recovery software that can scan a corrupted database and restore it successfully.
Stellar Phoenix SQL Recovery is a premier tool to repair damaged SQL databases and is supportive to SQL Server 2008, 2005 and 2000. With self-descriptive and exceptionally realistic interface, advanced repair options and non-destructive design, it is an effective SQL Repair tool to repair all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
For an instance, you might come across the similar error message with your SQL Server database:
“Database error: Page P_ID1 is marked with the wrong type in PFS page P_ID2. PFS status 0xVAL1 expected 0xVAL2.”
This error is marked as error 8948 in SQL Server error log.
Cause
The above error results when a page P_ID1 has been marked with incorrect type entry in PFS page P_ID2. As described above, each PFS page has a byte-map with one byte per page for all the pages included in the PFS interval. Among rest of the information, each byte contains three specific type of status bits that define the page type:
(0x10) for PFS_IS_IAM_PG
(0x40) for PFS_IS_ALLOCATED
(0x20)for PFS_IS_MIXED_EXT
Error 8948 occurs when these bits are improperly set.
Solution
You need to deploy these measures to cope up with such issues:
If such kind of problems are persistent in nature, you should check the system for possible hardware problems first. You can do so by examining the error log reports of Windows, SQL Server™ and application.
Check the database backup status. If complete and valid, delete the damaged database and restore from the backup.
Without using any repair clause, execute DBCC CHECKDB to determine the required repair clause to be applied. Next, run DBCC CHECKDB with this repair clause.
If you desire to prevent data loss that might occur due to the above step, you need to use advanced SQL Repair tools. These are safe SQL Recovery software that can scan a corrupted database and restore it successfully.
Stellar Phoenix SQL Recovery is a premier tool to repair damaged SQL databases and is supportive to SQL Server 2008, 2005 and 2000. With self-descriptive and exceptionally realistic interface, advanced repair options and non-destructive design, it is an effective SQL Repair tool to repair all database objects. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
Sunday, August 16, 2009
Error 2570 in SQL Server
SQL Server includes a database check utility called DBCC CHECKDB. In SQL Server 2005, you can use this command with DATA_PURITY option enabled that allows you to perform ‘data purity’ validations on each column value in all rows of a table or multiple tables from the database. If you run this check and it outputs error messages that indicates problems with data and hence database integrity. In such situations, you need to use your recent backup to restore the lost information. But, if you find it invalid or inappropriate to deliver required results, SQL Server Recovery tools can be used as a solution.
Consider a scenario, you check your database integrity using DBCC CHECKDB with DATA_PURITY option enabled and it gives the below error message:
“Msg 2570, Level 16, State 2, Line 1
Page %S_PGID, slot %d in Object %d Index %d Column %.*ls value %.*ls is out of range for data type "%.*ls". Update column to a legal value.”
This error message occurs for every row that contains an invalid column value.
Cause
The above error occurs due to invalid data in a column of a table as invalid floating point values as SNAN, QNAN, NINF, ND, PD, PINF etc. It can also happen due to out-of-range data or hardware issues.
Solution
To correct the above issue, you need to follow any of the below methods:
You should find the affected rows and manually update them with correct values. To do this, you can execute T-SQL (Transact-SQL) queries against the table or alternatively, refer to the information provided by error 2570. You can set it to any of acceptable default or specific value.
Note: You can’t run DBCC command to repair the database as it can’t determine
the value to be placed instead of invalid column value.
In case if affected rows are large in number and it is not possible to update them manually, you can restore them from backup
If the above measure is not feasible because of backup unavailability or corruption, you need to use MDF Recovery applications to safely repair and restore your database. Such MDF Repair software use powerful scanning algorithms and offer advanced repair and restoration options together with interactive user interface.
Stellar Phoenix SQL Recovery is the foremost SQL Repair tool to repair damaged SQL databases. With self-descriptive interface, advanced repair options and read-only nature, it is an effective tool to repair all database objects. It supports SQL Server 2005 and SQL Server 2000. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
Consider a scenario, you check your database integrity using DBCC CHECKDB with DATA_PURITY option enabled and it gives the below error message:
“Msg 2570, Level 16, State 2, Line 1
Page %S_PGID, slot %d in Object %d Index %d Column %.*ls value %.*ls is out of range for data type "%.*ls". Update column to a legal value.”
This error message occurs for every row that contains an invalid column value.
Cause
The above error occurs due to invalid data in a column of a table as invalid floating point values as SNAN, QNAN, NINF, ND, PD, PINF etc. It can also happen due to out-of-range data or hardware issues.
Solution
To correct the above issue, you need to follow any of the below methods:
You should find the affected rows and manually update them with correct values. To do this, you can execute T-SQL (Transact-SQL) queries against the table or alternatively, refer to the information provided by error 2570. You can set it to any of acceptable default or specific value.
Note: You can’t run DBCC command to repair the database as it can’t determine
the value to be placed instead of invalid column value.
In case if affected rows are large in number and it is not possible to update them manually, you can restore them from backup
If the above measure is not feasible because of backup unavailability or corruption, you need to use MDF Recovery applications to safely repair and restore your database. Such MDF Repair software use powerful scanning algorithms and offer advanced repair and restoration options together with interactive user interface.
Stellar Phoenix SQL Recovery is the foremost SQL Repair tool to repair damaged SQL databases. With self-descriptive interface, advanced repair options and read-only nature, it is an effective tool to repair all database objects. It supports SQL Server 2005 and SQL Server 2000. The software is compatible with Windows Vista, XP, 2003, 2000 and NT.
Thursday, August 13, 2009
The system cannot self repair this error - while accessing SQL database
Database Console Commands (DBCC) check the logical and physical consistency of the SQL database and can also resolve few detected error messages. But there are many issues that can not be resolved by using DBCC commands. In such scenarios, the SQL database corruption mainly occurs due to corrupt metadata, corruptions in certain critical system base tables or hardware failure. For absolute and systematic recovery of SQL database, the user needs to use effective SQL Recovery application.
The error message that appears when a user attempts to access SQL database is:
“The system cannot self repair this error”
After a user encounters the above error message, the data saved in the SQL database becomes inaccessible. The main cause of the above error message is SQL database corruption due to corrupt system database files, Page Free Space (PFS) page damage or corrupt metadata. Another main reason for the above error message can be faulty hardware. To resolve the above error and access the data in SQL database, the user needs to follow these steps:
1) The user can restore the database from latest backup.
2) The user can run DBCC commands with repair option. (For the above error message, the DBCC command can not repair the database.)
3) If there is a hardware issue, the user needs to replace the hard drive.
If the above measures fail to perform, then the user needs to recover the inaccessible data by using efficient SQL Server Recovery software. A SQL Recovery application incorporates advanced and powerful scanning algorithms to recover the lost data.
Stellar Phoenix SQL Database Recovery is the most advanced SQL Recovery software that repairs and restores the corrupted and damaged .mdf files from MS SQL Server database. With Stellar’s SQL repair software, you can perform complete SQL Database Recovery in all possible data loss scenarios. This read only SQL Repair application can Repair SQL objects including tables, views, saved procedures and triggers. It provides interactive and intuitive user interface and supports MS SQL Server 2005 and MS SQL Server 2000. This SQL Repair utility can also recover and restore the backup files of MS SQL Server.
The error message that appears when a user attempts to access SQL database is:
“The system cannot self repair this error”
After a user encounters the above error message, the data saved in the SQL database becomes inaccessible. The main cause of the above error message is SQL database corruption due to corrupt system database files, Page Free Space (PFS) page damage or corrupt metadata. Another main reason for the above error message can be faulty hardware. To resolve the above error and access the data in SQL database, the user needs to follow these steps:
1) The user can restore the database from latest backup.
2) The user can run DBCC commands with repair option. (For the above error message, the DBCC command can not repair the database.)
3) If there is a hardware issue, the user needs to replace the hard drive.
If the above measures fail to perform, then the user needs to recover the inaccessible data by using efficient SQL Server Recovery software. A SQL Recovery application incorporates advanced and powerful scanning algorithms to recover the lost data.
Stellar Phoenix SQL Database Recovery is the most advanced SQL Recovery software that repairs and restores the corrupted and damaged .mdf files from MS SQL Server database. With Stellar’s SQL repair software, you can perform complete SQL Database Recovery in all possible data loss scenarios. This read only SQL Repair application can Repair SQL objects including tables, views, saved procedures and triggers. It provides interactive and intuitive user interface and supports MS SQL Server 2005 and MS SQL Server 2000. This SQL Repair utility can also recover and restore the backup files of MS SQL Server.
Tuesday, August 11, 2009
SQL Server Error 2533 and Recovery
Database pages are the basic Input/Output unit of SQL Server. All these pages are marked with an individual 96-byte header. These headers store page metadata such as page type, page number, free space available on page and object/index ID. If SQL Server finds incorrect information in these page headers, it declares them corrupted and fails to access information from them. As a result, the corresponding tables get corrupted. Therefore, to restore the lost information, you need to use your recent data backup. At times, database backup is not available or exists in invalid state. In such situations, you should use advanced SQL recovery tools.
You might encounter the below error displaying in SQL Server error log:
Server: Msg 2533, Level 16, State 1
Table error: Page P_ID allocated to object ID O_ID, index ID I_ID was not seen. Page may be invalid or have incorrect object ID information in its header.
Cause
Error 2533 generates when the page is allocated, but SQL Server doesn’t find the expected object/index ID in page header. The page header shows invalid index ID, which indicates the page corruption in database. Such kinds of errors generally arise due to hardware malfunction.
Solution
To troubleshoot error 2533 in SQL Server, you should follow these methods:
You need to detect and correct hardware issues using hardware diagnostics. You can also check system, application and SQL Server™ log for this purpose.
If a clean database backup is available, you can use it to restore required information.
When no clean backup is available, you should run DBCC CHECKDB command without using any repair clause. It will allow you to determine the extent of database corruption and suggest the repair clause. Run DBCC CHECKDB command with the suggested repair clause. But, the process can cause data loss as will delete the corrupted pages.
If problem persists, use commercial SQL Repair tools. These are advanced and safe SQL Recovery applications designed to analyze and repair a damaged SQL Server database in all cases of logical corruption. Such tools embed powerful recovery options and provide graphically rich user interface.
Stellar Phoenix SQL Recovery is a comprehensive repair tool for damaged SQL Server databases. It supports safe database repair for SQL Server 2008, 2005 and 2000. This SQL Repair software provides self-descriptive interface and can restore all database objects including tables, user defined data types and functions, triggers, stored procedures etc.
You might encounter the below error displaying in SQL Server error log:
Server: Msg 2533, Level 16, State 1
Table error: Page P_ID allocated to object ID O_ID, index ID I_ID was not seen. Page may be invalid or have incorrect object ID information in its header.
Cause
Error 2533 generates when the page is allocated, but SQL Server doesn’t find the expected object/index ID in page header. The page header shows invalid index ID, which indicates the page corruption in database. Such kinds of errors generally arise due to hardware malfunction.
Solution
To troubleshoot error 2533 in SQL Server, you should follow these methods:
You need to detect and correct hardware issues using hardware diagnostics. You can also check system, application and SQL Server™ log for this purpose.
If a clean database backup is available, you can use it to restore required information.
When no clean backup is available, you should run DBCC CHECKDB command without using any repair clause. It will allow you to determine the extent of database corruption and suggest the repair clause. Run DBCC CHECKDB command with the suggested repair clause. But, the process can cause data loss as will delete the corrupted pages.
If problem persists, use commercial SQL Repair tools. These are advanced and safe SQL Recovery applications designed to analyze and repair a damaged SQL Server database in all cases of logical corruption. Such tools embed powerful recovery options and provide graphically rich user interface.
Stellar Phoenix SQL Recovery is a comprehensive repair tool for damaged SQL Server databases. It supports safe database repair for SQL Server 2008, 2005 and 2000. This SQL Repair software provides self-descriptive interface and can restore all database objects including tables, user defined data types and functions, triggers, stored procedures etc.
Monday, August 10, 2009
Resolving Error 8904 in SQL Server
In SQL Server database, there are few types of pages that are used to store allocation structures. A GAM (Global Allocation Map) page is the one that has an individual bit for each extent included in the file interval that GAM page maps. Whereas, SGAM (Shared GAM) has similar structure as of GAM but has little dissimilarity like in SGAM, each of set bits corresponds to an extent, where each of the pages is independently allocated to IAM pages for different indexes. An IAM page also retains the similar structure as of GAM page, but has one dedicated bit for an extent that is allocated to the index (here, the discussed index is the one of which IAM page is a part). But sometimes, you get table corruption errors that show that two different IAM pages have been allocated the same extent. In such situations, you are recommended to immediately restore your data from backup or use third-party SQL recoveryapplications to scan and repair such databases.
You might receive the below error with your SQL Server database:
Server: Msg 8904, Level 16, State 2
Extent E_ID in database ID DB_ID is allocated to more than one allocation object.
You might also get error 8913 explaining the details of indexes involved.
Cause
The above error signifies that the bits are in state 2 in the specified table, but with two different IAM pages while the same extent is allocated to both of them. These conditions usually arise due to hardware failure reasons.
Solution
It is suggested to first check your system for hardware failures. To do so, you should run hardware diagnostics, check the application and Windows error logs for the related hardware failure errors.
To cope up with database issues, use your recent data backup
If no clean backup is available, you should run DBCC CHECKDB command without using any repair clause. This will determine the extent of corruption and repair clause that should be used. Again run DBCC CEHCKDB but with using suggested repair clause. But the process can delete the corrupted database items while making it error-free.
To perform safe and efficient database repair, you need to use commercial SQL Repair utilities. These are designed as read-only applications that you can use to get complete SQL Recovery results.
Stellar Phoenix SQL Recovery is an advanced tool that repairs and restores damaged SQL Server database created with SQL Server 2008, 2005 and 2000. It is a comprehensive database repair product for all database objects and is embedded with unique set of features. It is compatible with Windows Vista, XP, 2003, 2000 and NT.
You might receive the below error with your SQL Server database:
Server: Msg 8904, Level 16, State 2
Extent E_ID in database ID DB_ID is allocated to more than one allocation object.
You might also get error 8913 explaining the details of indexes involved.
Cause
The above error signifies that the bits are in state 2 in the specified table, but with two different IAM pages while the same extent is allocated to both of them. These conditions usually arise due to hardware failure reasons.
Solution
It is suggested to first check your system for hardware failures. To do so, you should run hardware diagnostics, check the application and Windows error logs for the related hardware failure errors.
To cope up with database issues, use your recent data backup
If no clean backup is available, you should run DBCC CHECKDB command without using any repair clause. This will determine the extent of corruption and repair clause that should be used. Again run DBCC CEHCKDB but with using suggested repair clause. But the process can delete the corrupted database items while making it error-free.
To perform safe and efficient database repair, you need to use commercial SQL Repair utilities. These are designed as read-only applications that you can use to get complete SQL Recovery results.
Stellar Phoenix SQL Recovery is an advanced tool that repairs and restores damaged SQL Server database created with SQL Server 2008, 2005 and 2000. It is a comprehensive database repair product for all database objects and is embedded with unique set of features. It is compatible with Windows Vista, XP, 2003, 2000 and NT.
Sunday, August 9, 2009
Error 3403 in SQL Server
A SQL Server database is comprised of two basic components, viz. data files and transaction logs. A transaction log file is the one which records uncommitted transactions of database. If due to any reason, SQL Server service shuts down unexpectedly, the next time when you restart the server, it analyzes all the transaction log files and if not committed, it rolls back all the changes that have been performed as the part of such transactions. But sometimes, this recovery procedure fails to end successfully and database remains in corrupted state. Such situations require you to restore from the last good backup. However, if no backup is available or is damaged, you should use SQL Repair applications.
You might encounter the below error message with your SQL Server database:
Error 3403, Severity 22
During recovery initialization, page %ld was encountered. This page belongs to object %ld, not the log
Cause
After the SQL crash, SQL Server automatically tries to recover. While it occurs, it scans the complete transaction log till the last page. If it finds a page, which is allocated to syslogs but the object ID on the page header doesn’t match with that of syslogs, it displays error 3403 and recovery fails. It occurs because of following possible reasons:
A SQL Server problem resulted in a bad write or page allocation
Allocation page was updated and SQL Server went down before the transaction log page could be written. So, when later SQL database rebuilt itself, it did it without transaction log pages being cleared, while the old log entries still exist.
Solution
To solve such issues, you should apply these methods:
Check your backup status. If a clean backup exists, drop the damaged database and load it from the backup
If no valid backup exists, use commercial SQL Server Recovery applications to repair and restore the database
SQL Repair software are powerful and safe tools that use efficient scanning algorithms to repair a damaged SQL Server database. Such applications feature thorough file scanning, non-destructive design, graphically rich user interface and complete documentation.
Stellar Phoenix SQL Database Recovery is the finest SQL Recovery application that supports SQL Server 2008, 2005 and 2000. It can restore all database objects, including tables, views, stored procedures, rules, defaults, user defined data types and triggers. The software is compatible with Windows Vista, XP, 2003, 2000 and NT. It is a non-destructive tool with intuitive interface.
You might encounter the below error message with your SQL Server database:
Error 3403, Severity 22
During recovery initialization, page %ld was encountered. This page belongs to object %ld, not the log
Cause
After the SQL crash, SQL Server automatically tries to recover. While it occurs, it scans the complete transaction log till the last page. If it finds a page, which is allocated to syslogs but the object ID on the page header doesn’t match with that of syslogs, it displays error 3403 and recovery fails. It occurs because of following possible reasons:
A SQL Server problem resulted in a bad write or page allocation
Allocation page was updated and SQL Server went down before the transaction log page could be written. So, when later SQL database rebuilt itself, it did it without transaction log pages being cleared, while the old log entries still exist.
Solution
To solve such issues, you should apply these methods:
Check your backup status. If a clean backup exists, drop the damaged database and load it from the backup
If no valid backup exists, use commercial SQL Server Recovery applications to repair and restore the database
SQL Repair software are powerful and safe tools that use efficient scanning algorithms to repair a damaged SQL Server database. Such applications feature thorough file scanning, non-destructive design, graphically rich user interface and complete documentation.
Stellar Phoenix SQL Database Recovery is the finest SQL Recovery application that supports SQL Server 2008, 2005 and 2000. It can restore all database objects, including tables, views, stored procedures, rules, defaults, user defined data types and triggers. The software is compatible with Windows Vista, XP, 2003, 2000 and NT. It is a non-destructive tool with intuitive interface.
Thursday, August 6, 2009
Unexpected SQL Server Connection Termination
Microsoft SQL Server is the popular relational model database server used to create, edit and maintain featured databases. MS SQL Server comes available in various editions, like SQL Server Compact Edition, SQL Server Evaluation Edition, SQL Server Developer Edition and others such. But at times, you observe that SQL Server looses its connection. Without giving any error message, the connection terminates unexpectedly. One of the possible reasons is database corruption and hence, to restore the lost information, you should use your recent data backup. But in case of backup issues, it is recommended to safely repair your database using commercial SQL Server Recovery tools.
Consider a practical scenario; you start the system and SQL Server terminates the connection, with or without displaying an error message. You cannot rebuild the connection in subsequent attempts.
Cause
SQL Server terminates the connection if any of the below conditions is true:
SQL Server process has suffered an execution error, for example, it is trying to access an illegal memory address or SQL Server encounters assertion error or stack overflow
A protocol error has occurred in the communication between SQL Server and client library. It could occur due to listed reasons:
Bugs in client library or SQL Server
Hardware issues
Network problems
Resource problems
SQL Server database corruption
Solution
To correct these problems, you are required to consider these methods:
Try reinstalling SQL server
Reinstall client library
Troubleshoot hardware problems. You need to use hardware diagnostic utility to detect malfunctioned hardware
Detect and correct networking problems.
To correct resource issues, ensure that sufficient RAM and disk space are available
If database is corrupt, run DBCC CHECKDB command to check. If it reports corruption, use this command with REPAIR_DATA_LOSS command. But it deletes all the damaged information. Thus for safe repair, it is recommended to use third party SQL Repair applications. These SQL Recovery software employ advanced scanning algorithms to analyze the damaged database and repair them intact. In addition, they provide automated database repair functionalities together with read-only design.
Stellar Phoenix SQL Recovery is a premier tool that repairs damaged SQL Server databases. It supports SQL Repair for SQL Server 2000 and 2005. This software provides self-explanatory interface and restores all database objects including tables, user defined data types and functions, triggers, stored procedures, views, rules etc. This SQL Recovery software is compatible with Windows Vista, XP, 2003, 2000, and NT.
Consider a practical scenario; you start the system and SQL Server terminates the connection, with or without displaying an error message. You cannot rebuild the connection in subsequent attempts.
Cause
SQL Server terminates the connection if any of the below conditions is true:
SQL Server process has suffered an execution error, for example, it is trying to access an illegal memory address or SQL Server encounters assertion error or stack overflow
A protocol error has occurred in the communication between SQL Server and client library. It could occur due to listed reasons:
Bugs in client library or SQL Server
Hardware issues
Network problems
Resource problems
SQL Server database corruption
Solution
To correct these problems, you are required to consider these methods:
Try reinstalling SQL server
Reinstall client library
Troubleshoot hardware problems. You need to use hardware diagnostic utility to detect malfunctioned hardware
Detect and correct networking problems.
To correct resource issues, ensure that sufficient RAM and disk space are available
If database is corrupt, run DBCC CHECKDB command to check. If it reports corruption, use this command with REPAIR_DATA_LOSS command. But it deletes all the damaged information. Thus for safe repair, it is recommended to use third party SQL Repair applications. These SQL Recovery software employ advanced scanning algorithms to analyze the damaged database and repair them intact. In addition, they provide automated database repair functionalities together with read-only design.
Stellar Phoenix SQL Recovery is a premier tool that repairs damaged SQL Server databases. It supports SQL Repair for SQL Server 2000 and 2005. This software provides self-explanatory interface and restores all database objects including tables, user defined data types and functions, triggers, stored procedures, views, rules etc. This SQL Recovery software is compatible with Windows Vista, XP, 2003, 2000, and NT.
Wednesday, August 5, 2009
SQL Server Page Header Corruption and Error 8939
SQL Server database storage space is divided into pages, which are numbered sequentially. When you perform any operation, these pages serve as the basic I/O unit. Each of these pages is marked with a corresponding header (96-byte in size) that conveys information like page number, free space available, page type, object ID etc. If you run DBCC CHECKDB on database and it reports errors on database pages, the odds are that the page header is damaged. This leads to data inaccessibility and to restore lost information, you require using your recent data backup. However, if backup is damaged, not updated, or not available, you need to use SQL recovery tools for safe repair and restoration.
Consider a practical instance, you run DBCC CHECKDB on your SQL Server database and get a series of error messages, similar to:
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID O_ID, index ID I_ID, partition PA_ID, alloc unit ID AU_ID, page P_ID, Test (TEST) failed. Values are VAL1 and VAL2.
Cause
Error 8939 arises due to corruption in page header. One of the possible causes is hardware errors. The test that failed is defined in TEST string, while VAL1 and VAL2 are dependent upon error state.
Solution
To correct the above error, you need to follow these steps:
You require examining system and application logs for hardware failures. Replace the affected hardware components. Also, you need to ensure that no write caching is enabled on disk controller (this is the issue when data corruption is observed frequently)
Use your recent data backup to restore lost data.
In case of valid backup unavailability, run DBCC CHECKDB command to determine corruption state and repair clause to be used. Next, you need to run DBCC CHECKDB with recommended repair clause. Note: This process results into data loss as the affected pages will be deleted.
For safe SQL Repair, use commercial repair applications. SQL Recovery software are read-only, advanced, and automated software that scan damaged databases and restore them with original content and view.
Stellar Phoenix SQL Recovery is a comprehensive repair tool for damaged SQL Server databases. It supports SQL Server 2000 and 2005. This SQL Repair software is available with self-descriptive interface and restores all database objects (tables, user defined data types and functions, triggers, stored procedures, views, rules etc.). The software is compatible with Windows Vista, XP, 2003, 2000, and NT.
Consider a practical instance, you run DBCC CHECKDB on your SQL Server database and get a series of error messages, similar to:
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID O_ID, index ID I_ID, partition PA_ID, alloc unit ID AU_ID, page P_ID, Test (TEST) failed. Values are VAL1 and VAL2.
Cause
Error 8939 arises due to corruption in page header. One of the possible causes is hardware errors. The test that failed is defined in TEST string, while VAL1 and VAL2 are dependent upon error state.
Solution
To correct the above error, you need to follow these steps:
You require examining system and application logs for hardware failures. Replace the affected hardware components. Also, you need to ensure that no write caching is enabled on disk controller (this is the issue when data corruption is observed frequently)
Use your recent data backup to restore lost data.
In case of valid backup unavailability, run DBCC CHECKDB command to determine corruption state and repair clause to be used. Next, you need to run DBCC CHECKDB with recommended repair clause. Note: This process results into data loss as the affected pages will be deleted.
For safe SQL Repair, use commercial repair applications. SQL Recovery software are read-only, advanced, and automated software that scan damaged databases and restore them with original content and view.
Stellar Phoenix SQL Recovery is a comprehensive repair tool for damaged SQL Server databases. It supports SQL Server 2000 and 2005. This SQL Repair software is available with self-descriptive interface and restores all database objects (tables, user defined data types and functions, triggers, stored procedures, views, rules etc.). The software is compatible with Windows Vista, XP, 2003, 2000, and NT.
Monday, August 3, 2009
The system cannot self repair this error - while accessing SQL database
Database Console Commands (DBCC) check the logical and physical consistency of the SQL database and can also resolve few detected error messages. But there are many issues that can not be resolved by using DBCC commands. In such scenarios, the SQL database corruption mainly occurs due to corrupt metadata, corruptions in certain critical system base tables or hardware failure. For absolute and systematic recovery of SQL database, the user needs to use effective SQL Recovery application.
The error message that appears when a user attempts to access SQL database is:
“The system cannot self repair this error”
After a user encounters the above error message, the data saved in the SQL database becomes inaccessible. The main cause of the above error message is SQL database corruption due to corrupt system database files, Page Free Space (PFS) page damage or corrupt metadata. Another main reason for the above error message can be faulty hardware. To resolve the above error and access the data in SQL database, the user needs to follow these steps:
1) The user can restore the database from latest backup.
2) The user can run DBCC commands with repair option. (For the above error message, the DBCC command can not repair the database.)
3) If there is a hardware issue, the user needs to replace the hard drive.
If the above measures fail to perform, then the user needs to recover the inaccessible data by using efficient SQL recovery software. A SQL Recovery application incorporates advanced and powerful scanning algorithms to recover the lost data.
Stellar Phoenix SQL Database Recovery is the most advanced SQL Recovery software that repairs and restores the corrupted and damaged .mdf files from MS SQL Server database. With Stellar’s SQL repair software, you can perform complete SQL Database Recovery in all possible data loss scenarios. This read only SQL Repair application can Repair SQL objects including tables, views, saved procedures and triggers. It provides interactive and intuitive user interface and supports MS SQL Server 2005 and MS SQL Server 2000. This SQL Repair utility can also recover and restore the backup files of MS SQL Server.
The error message that appears when a user attempts to access SQL database is:
“The system cannot self repair this error”
After a user encounters the above error message, the data saved in the SQL database becomes inaccessible. The main cause of the above error message is SQL database corruption due to corrupt system database files, Page Free Space (PFS) page damage or corrupt metadata. Another main reason for the above error message can be faulty hardware. To resolve the above error and access the data in SQL database, the user needs to follow these steps:
1) The user can restore the database from latest backup.
2) The user can run DBCC commands with repair option. (For the above error message, the DBCC command can not repair the database.)
3) If there is a hardware issue, the user needs to replace the hard drive.
If the above measures fail to perform, then the user needs to recover the inaccessible data by using efficient SQL recovery software. A SQL Recovery application incorporates advanced and powerful scanning algorithms to recover the lost data.
Stellar Phoenix SQL Database Recovery is the most advanced SQL Recovery software that repairs and restores the corrupted and damaged .mdf files from MS SQL Server database. With Stellar’s SQL repair software, you can perform complete SQL Database Recovery in all possible data loss scenarios. This read only SQL Repair application can Repair SQL objects including tables, views, saved procedures and triggers. It provides interactive and intuitive user interface and supports MS SQL Server 2005 and MS SQL Server 2000. This SQL Repair utility can also recover and restore the backup files of MS SQL Server.
Sunday, August 2, 2009
Resolving Error 5171 in SQL Database
SQL Server database file (MDF file) corruption or damage can occur due to SQL Server malfunctioning, improper server shutdown, virus infection, hardware failure and more. Once the SQL database gets corrupted, the SQL database can become completely inaccessible. In such situations, if there is no backup available, the user needs to perform SQL database repair by using advanced SQL Repair application.
Consider a practical scenario, where a user is working on SQL Server 2005 and creating a report. While doing so, the Windows server restarts due to power failure and the user encounters an abrupt server restart screen prompting for the reason and information. Due to the operating system issue, the SQL database becomes inaccessible. When the user tries to attach the MDF manually, he encounters the below error message:
“An exception occurred while executing a Transact-SQL statement or batch._db.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171).”
Or
“C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MYDATABASE.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171)”
In such circumstances, the database administrators recommend to attach a single file. However, when the user uses sp_attach_single_db Stored Procedures, the user encounters the following error message:
“Server: Msg 5172, Level 16, State 15, Line 1
The header for file path……\.mdf is not a valid database file header. The PageAudit property is incorrect.”
Cause:]
The main cause of the above error message is MDF file corruption. The above issue occurs when the MDF file header gets corrupted or due to insertion of some invalid information in the header file. All these situations result in inaccessibility of the SQL database. To ensure complete accessibility of the SQL database, the user needs to recover it from the latest backup. But if the user has not created any backup of the inaccessible MDF file, then he needs to perform MDF repair. To do so, the user needs to use effective SQL repair application. Such applications incorporate advanced and powerful scanning methods to repair the corrupted MDF file. The recovery software perform systematic scan of corrupted MDF files, repair and restore them in their original format without altering any information.
Stellar Phoenix SQL Database Recovery is the most trustworthy SQL recovery software. This repair software can Repair SQL objects such as, tables, reports, forms, macros, database constraints, stored procedures, triggers etc. It supports SQL Server 2005 and 2000. It is compatible with Windows Vista, XP, 2003 and 2000.
Consider a practical scenario, where a user is working on SQL Server 2005 and creating a report. While doing so, the Windows server restarts due to power failure and the user encounters an abrupt server restart screen prompting for the reason and information. Due to the operating system issue, the SQL database becomes inaccessible. When the user tries to attach the MDF manually, he encounters the below error message:
“An exception occurred while executing a Transact-SQL statement or batch.
Or
“C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MYDATABASE.mdf is not a primary database file. (Microsoft SQL Server, Error: 5171)”
In such circumstances, the database administrators recommend to attach a single file. However, when the user uses sp_attach_single_db Stored Procedures, the user encounters the following error message:
“Server: Msg 5172, Level 16, State 15, Line 1
The header for file path……\.mdf is not a valid database file header. The PageAudit property is incorrect.”
Cause:]
The main cause of the above error message is MDF file corruption. The above issue occurs when the MDF file header gets corrupted or due to insertion of some invalid information in the header file. All these situations result in inaccessibility of the SQL database. To ensure complete accessibility of the SQL database, the user needs to recover it from the latest backup. But if the user has not created any backup of the inaccessible MDF file, then he needs to perform MDF repair. To do so, the user needs to use effective SQL repair application. Such applications incorporate advanced and powerful scanning methods to repair the corrupted MDF file. The recovery software perform systematic scan of corrupted MDF files, repair and restore them in their original format without altering any information.
Stellar Phoenix SQL Database Recovery is the most trustworthy SQL recovery software. This repair software can Repair SQL objects such as, tables, reports, forms, macros, database constraints, stored procedures, triggers etc. It supports SQL Server 2005 and 2000. It is compatible with Windows Vista, XP, 2003 and 2000.
Subscribe to:
Posts (Atom)