Fixing “Errors found in text ID TEXT_ID...” Error Message

DBCC CHECKDB is a repair command used by MS SQL Server users to detect and repair their corrupt databases. The command can be used with various parameters, such as, repair_rebuild and repair_allow_data_loss. Although the command proves helpful in resolving all kinds of logical corruption issues, there are certain problems that persists even after using the above command. Such situations occur when the database is badly corrupted. An easy way to access data in case of severe corruption is by restoring the database from an updated backup. However, in case of no backup available or backup falling short of restore the required database, you will need to use a powerful third-party MDF File Repair application. Consider a real-time situation to describe the above problem. You attempt to mount your SQL database and see some consistency issues. To resolve these issues, when you run DBCC CHECKDB command, you encounter the below error message: “Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 379493089280 owned by data record identified by RID = (1:647611:14) PK1 = 1300583. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 379544338432 owned by data record identified by RID = (1:648136:32) PK1 = 1300903. … Table error: Object ID 1979154096, index ID 255, page (1:558593). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 0, text ID 552407334912 is referenced by page (1:1387313), slot 46, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 … CHECKDB found 0 allocation errors and 33 consistency errors in table 'QTI_RESULT_DATA' (object ID 1979154096). CHECKDB found 0 allocation errors and 33 consistency errors in database 'bb_bb60'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (bb_bb60 ).” After the above error message gets displayed on the screen, the database records become inaccessible. Cause: The root cause for DBCC CHECKDB command to display the above error message is severe corruption of MS SQL database. Resolution: Below are some guidelines that help you to overcome the above error message: Check if any system component is physically damaged. To do so, check the system, application, and SQL Server logs. Identify the component in the logs and swap it with a new component.

Run DBCC CHECKDB command with repair_allow_data_loss parameter. However, doing so might erase some of the critical data saved in your database.