Microsoft SQL server supports LOB (Large Object) data types to store the very large amount (Maximum size is 4 Gigabytes) of data. These data types are CLOB (Character LOB), BLOB (Binary LOB) and DBCLOB (Double-Byte Character LOB).Structures of these data types are different from regular data types. Sometimes SQL server generates Error 7105 due to LOB referred by database page can’t be accessible. Continue reading this article, you will find resolution for this.
Error Message 7105: When error 7105 occurs in SQL server then we can see the following error message on the screen-
Msg 7105, Level 22, State 6, Line 1
The Database ID 11, Page (255:177), slot 1 for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE
Note:In this error Severity Level is 22 which mean connection is terminated by the server.
Reasons of error 7105 in MS SQL: This error can be occur by the following reasons –
Solutions: You can use the following methods to repair SQL Database-
Error Message 7105: When error 7105 occurs in SQL server then we can see the following error message on the screen-
Msg 7105, Level 22, State 6, Line 1
The Database ID 11, Page (255:177), slot 1 for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE
Note:In this error Severity Level is 22 which mean connection is terminated by the server.
Reasons of error 7105 in MS SQL: This error can be occur by the following reasons –
- Database corruption issue lies within a database page or LOB (Large Object) structure.
- The query that fails with READ UNCOMMITED ISOLATION or NOLOCK query hint.
- When SQL server engine causing the query to fail with the same error.
Solutions: You can use the following methods to repair SQL Database-
- Run DBCC CHECKDB against the database or DBCC CHECKTABLE against the table where the problem was encountered.
- If the problem is linked with the database query then rewrite and rerun the same.
- If the problem is related to SQL server engine then update the server with latest service pack.
- Restore the .mdf file from the last backup.
I got the exactly same error in my SQL database. I followed your solution steps and my database had been repaired. Thanks for the wonderful post.
ReplyDeleteThank you and it is a pleasure to help all the readers.
ReplyDelete