Tuesday, December 14, 2010
DBCC CHECKDB Displays 8929 Error Message
MS SQL Server database users use DBCC CHECKDB command to repair their logically damaged SQL databases. This command can be used with different 'repair' parameters, such as, repair_allow_data_loss, repair_fast, and repair_rebuild. While the command used with the above parameters performs maximum repair in most database corruption cases, there might be few instances, wherein the command fails to resolve the corruption issues. In such cases, the output of the command is an error message, which states the exact cause for failure of DBCC CHECKDB command. After the occurrence of DBCC CHECKDB command failure error message, the database remains unrepairable, further resulting in inaccessibility of saved records. To overcome such SQL database corruption scenarios and successfully access the records saved in the database (in case no backup is available), the user needs to opt for a commercial SQL Database Repair application. Below is one such error message that appears when the user DBCC CHECKDB command fails to repair a corrupted MS SQL database: “Server: Msg 8929, Level 16, State 1, Line 1 Object ID 2: Errors found in text ID 852426752 owned by data record identified by RID = (1:110:19) id = 1925581898 and indid = 2. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:438), slot 3, text ID 852426752 is referenced by page (1:71), slot 4, but was not seen in the scan. DBCC results for 'PDP'. DBCC results for 'sysobjects'. There are 652 rows in 11 pages for object 'sysobjects'. DBCC results for 'sysindexes'. There are 480 rows in 18 pages for object 'sysindexes'. CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2). DBCC results for 'syscolumns'...” After the above severity level 16 error message appears, the database records become inaccessible. Cause: The primary reason for the occurrence of above error message is severe corruption in MS SQL database. Resolution: To resolve the above error and mount your database, you will need to repair the database using a commercial SQL Database Repair software. A MS SQL Repair utility assures maximum repair of SQL database, irrespective of its level of corruption. SQL Recovery Software is a complete solution for repairing logically damaged MS SQL Server 2008, 2005, and 2000 database. It is competent enough to recover almost all database components after repairing. The read-only tool SQL Repair does not make any change in the original database. It can be installed on Windows 7, Vista, 2008, XP, 2003, and 2000 operating systems.