subject: Troubleshooting Error 8936 to overcome errors in the B-tree in MS SQL Server 2000 database [print this page] Although the B-tree is an important and useful part of the databases as it improves the overall performance by speeding up the operations, and is reliable. Most importantly, it keeps the data in a managed form, which makes working on the B-tree a hassle-free experience. Having said that, at times the nodes of the B-tree behave strangely, which prompts several error messages. You should correct such errors to perform SQL recovery. If it is not possible, then such problems should be sorted out by using a third-party SQL database recovery software.
Let us consider a scenario in which you encounter the following table error in an MS SQL Server 2000 database:
"Table error: Object ID O_ID, index ID I_ID. B-tree chain linkage mismatch. P_ID1->next = P_ID2, but P_ID2->Prev = P_ID3."
Cause:
The most prominent cause of this error is that there is some logical problem in the B-tree of the database. Actually, a P_ID1 page points to the P_ID2 page in the next page pointer but the previous page pointer of P_ID2 page points to P_ID3 page, which is incorrect.
Resolution:
To fix this table error, you need to perform either of the following methods, ideally in the given order:
Addressing hardware problems that caused error: At times, these errors are caused by faulty hardware parts that make data storage impossible. You can overcome this problem by doing the following tasks:
Fixing the hardware-related errors that are noted in the Server logs.
Rectifying the errors that occur after running hardware diagnostics.
Swapping hardware components to see where the problem actually lies.
Verifying if write-caching is enabled in the disks. If yes, then contact the hardware provider to replace the disk.
Using the database backup: If the hardware seems to be in place, then you should use the backup if it is clean and updated.
Executing DBCC CHECKDB: If the backup does not provide the solution, then you should run the DBCC CHECKDB tool to repair damaged SQL database.
Using these methods, you would be able to resolve the problem and recover SQL database. However, if the problem persists then you should use a third-party MS SQL Server recovery software to perform MDF file recovery. Having rich user interface along with superb user documentation, these read-only tools ensure safe and secure .MDF recovery.
The best SQL recovery software, which is recommended by most database recovery experts is Stellar Phoenix SQL Data Recovery. Recovering MDF files created for MS SQL Server 7.0, 2000, 2005, and 2008, this master database file recovery utility recovers various objects including NDF files, collations, tables, stored procedures, defaults, etc. This SQL recovery software is compatible with Windows 7, Server 2008, Vista, Server 2003, XP, and 2000.
Troubleshooting Error 8936 to overcome errors in the B-tree in MS SQL Server 2000 database
