Dbcc Checkdb Unable To Resolve Error 8909 And 8905

Corruption in SQL database is a common phenomenon faced by most of the database users

. While the reasons of corruption might differ, the resolution for most of the corruption scenarios remains the same DBCC CHECKDB command. The safest repair command comprehensively checks the physical and logical integrity of all the components in your database. It does so by performing three operations-DBCC CHECKALLOC, DBCC CHECKTABLE, and DBCC CHECKCATALOG. Although, the command repairs your database in most cases, there are certain error messages that are beyond the limit of this command. Moreover, there is also a possibility that the command might inform the user that the error has been resolved, even though it hasn't. In such situations, an ideal way to access your data is by restoring the data from latest database backup. However, there have been situations where it is not feasible to restore the data from the backup. In such case, use effective SQL Repair application.

Consider a practical scenario, where you receive any of the below error messages while attempting to access your database:

Server: Msg 8905, Level 16, State 1, Line 1

Extent (1:192) in database ID 10 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Or

Server: Msg 8909, Level 16, State 1, Line 1

Table error: Object ID 0, index ID 0, page ID (1:192). The PageId in the page header = (0:0).

The database records become inaccessible after the above error messages appear.

Cause

The above error message primarily occurs for the pages and extents that are allocated for sorting. These pages hold the below values:

Object ID is 0.

Page type is set to SORT_PAGE (7).

Index ID is 0.

Resolution

To resolve both the above error messages, you will need to run DBCC CHECKDB command. While the command reports that both error messages have be resolve, the fact is that they have not been fixed. Another resolution for the error messages can be obtaining the latest service pack for Microsoft SQL Server 2000. However, if both the resolutions fail to resolve your problem, then you will need to use advanced third-party SQL Repair application to repair your database. These sql repair tools ensures orderly and systematic repair of corrupted database, regardless of its cause of corruption.

SQL Recovery is an tool that surpasses all the other repair sql database applications. The repairing algorithms used by the software ensure complete repair of SQL Server 2008, 2005, and 2000 databases. The repair tool is designed for Windows 7, Vista, XP, 2003, 2000 and NT.

by: Adishree Singh

POST COMMENT

Repair Removable Disk It Support In Miami For Data Security And A Competitive Edge Doc File Got Corrupt When Opened With Frontpage Bkf File Corruption On A Fat Based File System Importance Of Compact Flash 32gb In The Market Data Recovery Post Powerpoint File Corruption Recover Contacts Sim Card Disaster Recovery Best Practices How To Make Lotus Notes To Outlook Conversion Time-efficient Some Latest Information About R4 Dsi Error 1413 When Restoring Itunes Export Emails From Lotus Notes To Outlook With Nsf To Pst Tool Error Messages While Restoring The Ms Sql Server Database