Error 7105 followed by The Database ID X, Page (1:XXXXXX), slot X for LOB data type node does not exist. error

Error 7105 followed by The Database ID X, Page (1:XXXXXX), slot X for LOB data type node does not exist. error by Juliane Padrão

Closed

as Not Reproducible Help for as Not Reproducible

Type:	Bug
ID:	361624
Opened:	8/13/2008 6:24:23 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Hi,
I have an instance of SQL Server 2005 Enterprise Edition with four databases which are being mirrored (Database Mirroring).
One of these databases is frequently showing the error 7105 followed by this message error:
"The Database ID X, Page (1:XXXXXX), slot X 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."

The isolation level is READ UNCOMMITED, which is the SQL Server default.

I ran checktable and checkdb on the table/database to find inconsistency problems, but no errors were returned. I looked for this error over the internet and found that there was a bug related with this error messages in SQL Server 2000, but no issues related to SQL Server 2005.

I know that the error message is associated with an Image field that this table has.
When I received this error message in SQL Log, I did the following steps to replicate the error in real time:

1 - Get the Page and slot numbers genereted by the error in SQL Log

2 - Run the commands:
DBCC TRACEON(3604);
DBCC PAGE (XXXX, 1, 20962, 1); --using information given by SQL Log

3 - In the list of slot information showed up, go to slot with the message error mentioned and look at the information of content of the data, for instance:

00000000: 48005400 0000dfd8 05000000 00002c00 †H.T...........,.
00000010: 02000000 484f5350 45444147 454d2044 †....HOSPEDAGEM D
00000020: 41532053 52544153 2e204c55 43494120 †AS SRTAS. LUCIA
00000030: 4f54412f 54414e49 41205341 4e544f53 †OTA/TANIA SANTOS
00000040: 30384a75 6e686f2f 32303038 73b74601 †08Junho/2008s.F.
00000050: 5c2ae116 a7040000 01001a00 ac5fdf00 †\*..........._..
00000060: 0000†††††††††††††††††††††††††††††††††..

4 - Get the piece of the data, for example "OTA/TANIA SANTOS" and form a SELECT statment filtering by the image field, for example: select * from spe.nfe_notasfiscais where discriminacao like '%OTA/TANIA SANTOS%'

5 - The same error is returned:
"The Database ID X, Page (1:XXXXXX), slot X 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."

So, after a few seconds, If I try to execute again the select statment this error vanished and the select works perfectly!

This error is boring and drive me nuts. I have an application that access this table, and the same exception is sent to it, causing a runtime error.

I would like an answer to workaround this problem.

Thanks
Juliane Padrão

Details (expand)

English

SQL Server 2005 SP2 - Enterprise Edition

SQL Engine

Win2003 Standard Server (SP2)

US English

1 - Get the Page and slot numbers genereted by the error in SQL Log

2 - Run the commands:
DBCC TRACEON(3604);
DBCC PAGE (XXXX, 1, 20962, 1); --using information given by SQL Log

3 - In the list of slot information showed up, go to slot with the message error mentioned and look at the information of content of the data, for instance:

00000000: 48005400 0000dfd8 05000000 00002c00 †H.T...........,.
00000010: 02000000 484f5350 45444147 454d2044 †....HOSPEDAGEM D
00000020: 41532053 52544153 2e204c55 43494120 †AS SRTAS. LUCIA
00000030: 4f54412f 54414e49 41205341 4e544f53 †OTA/TANIA SANTOS
00000040: 30384a75 6e686f2f 32303038 73b74601 †08Junho/2008s.F.
00000050: 5c2ae116 a7040000 01001a00 ac5fdf00 †\*..........._..
00000060: 0000†††††††††††††††††††††††††††††††††..

4 - Get the piece of the data, for example "OTA/TANIA SANTOS" and form a SELECT statment filtering by the image field, for example: select * from spe.nfe_notasfiscais where discriminacao like '%OTA/TANIA SANTOS%'

5 - The same error is returned:
"The Database ID X, Page (1:XXXXXX), slot X 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."

Error: 7105, Severity: 22, State: 6.

The Database ID X, Page (1:XXXXXX), slot X 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.

No errors

0 attachments

Posted by brimhj on 1/12/2012 at 7:38 PM

I have the same issue in 2008 R2 SP1. It is occurring on a Mirrored database.

Posted by Microsoft on 3/17/2009 at 6:36 PM

This issue is being closed as we don't have the repro. We will need to stack trace and process dump to undertand what is causing it. Please feel free to contact us if you are not satisfied with this resolution.

thanks
Sunil

Posted by SQL akuten on 9/24/2008 at 5:27 AM

same problem. The suggestion to run Run DBCC CHECKTABLE is pointless. I get no error from Run DBCC CHECKTABLE.

Posted by SQL akuten on 9/24/2008 at 5:27 AM

same problem. The suggestion to run Run DBCC CHECKTABLE is pointless. I get no error from Run DBCC CHECKTABLE.

Posted by Microsoft on 8/20/2008 at 11:29 AM

Feedback from dev is that we will need repro/stack dump. Also, we recommend you to contact CSS first. Without fully understanding the issue, it is hard to suggest a workaround.

Posted by Microsoft on 8/20/2008 at 10:02 AM

thanks for clarifying. This will need to be looked by the Dev. Have you contacted CSS for this issue?

Posted by Juliane Padrão on 8/19/2008 at 10:36 AM

Sorry about my mistake, our isolation level is read committed. I'm running this query on a principal database. When I said "with four databases which are being mirrored" I supose to say that our instance are beeing mirrored and not running aplications and queries against mirror database. Just to clarify.
Thanks

Posted by Microsoft on 8/18/2008 at 3:54 PM

thanks for contacting microsoft. I am not clear on your repro. Are you running this query on mirrored database? Mirror does not support querying. you will need to create a snapshot. Also, you indicated that the default isolation is 'read uncommitted' but actually it is read committed. The error 7105 can come under read uncommitted. So will appreciate clarifications. Thanks.