Error: 7886, Severity: 20, State: 1.

Hi All

I am seeing this error being logged in my SQL 2005 Ent machine

A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.

It seems to be arising out of a read of a text column.

Any info on this will be appreciated. Thanks

K T

You're not running CTP version, right?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=233339&SiteID=1|||

No

Its build 9.0.2153

|||

Hi Kts,

Do you use Row versioning in you database?

I waiting for your answer.

Regards,

|||

No !

|||

Hi kts,

What you TRANSACTION ISOLATION LEVEL do you run the code?

Can you post the query here?

Regards,

|||

hi

Like the message says READ UNCOMMITTED . its actually just a select with NO LOCK. The problem is I can only guess which proc it is but not know for sure as I am not able to recreate the problem manually.

|||

Ah, you use 'nolock' hint. There are issues with using such hint. I suggest you take a look at the following KB.

http://search.support.microsoft.com/kb/235880

|||

I'm still having the same problem..

My sql query results about 100Mb of information.

What can I do?

Error: 7886, Severity: 20, State: 1.

Hi All

I am seeing this error being logged in my SQL 2005 Ent machine

A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.

It seems to be arising out of a read of a text column.

Any info on this will be appreciated. Thanks

K T

You're not running CTP version, right?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=233339&SiteID=1|||

No

Its build 9.0.2153

|||

Hi Kts,

Do you use Row versioning in you database?

I waiting for your answer.

Regards,

|||

No !

|||

Hi kts,

What you TRANSACTION ISOLATION LEVEL do you run the code?

Can you post the query here?

Regards,

|||

hi

Like the message says READ UNCOMMITTED . its actually just a select with NO LOCK. The problem is I can only guess which proc it is but not know for sure as I am not able to recreate the problem manually.

|||

Ah, you use 'nolock' hint. There are issues with using such hint. I suggest you take a look at the following KB.

http://search.support.microsoft.com/kb/235880

|||

I'm still having the same problem..

My sql query results about 100Mb of information.

What can I do?

Error: 3314 serverity: 21, state: 4

I have this error, and it auto recovery after 1 minutes.. any idea? and it
involved more then one db.
Error while undoing logged operation in database 'hash'. Error at log record
i (20969:622890:4)..
Error : 9901,Severity: 21, state 1
the log file for database 'hash' is not available
Database hash cannot be open, it has been marked suspect for recovery, see
the sql server errorlog for more information.
starting up database 'hash'soonyu wrote:
> I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log record
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>
Is this a new installation, or one that has been running for a while?
Do you have any "bad block" events in your Windows Event Log around this
same time? My initial guess would be some sort of drive failure.|||This run for quite sometime.. more then year..
just notices this happen and twice already for this month..
first time, 2 db and auto recovery within one minutes..
second time, 1 db and auto recovery within one minutes as well..
Can't find any error.. and this is problem..
anybody have this kind of experience..
developer start mention about db problem..
soonyu.
"Tracy McKibben" wrote:
> soonyu wrote:
> > I have this error, and it auto recovery after 1 minutes.. any idea? and it
> > involved more then one db.
> >
> > Error while undoing logged operation in database 'hash'. Error at log record
> > i (20969:622890:4)..
> > Error : 9901,Severity: 21, state 1
> > the log file for database 'hash' is not available
> > Database hash cannot be open, it has been marked suspect for recovery, see
> > the sql server errorlog for more information.
> > starting up database 'hash'
> >
> Is this a new installation, or one that has been running for a while?
> Do you have any "bad block" events in your Windows Event Log around this
> same time? My initial guess would be some sort of drive failure.
>|||Perhaps you have auto-close turned on and some other process (like anti-virus) is opening the file?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
>I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log record
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>|||ok .. i will do two thing tommrow
1. check got bad block
2. check auto-close turned on?
3. antivirus scan/open this file?
but do you think auto-close will affected? auto-close you try to mentiion is
from sql enterprise manager->database->option->auto-close?
hopefully is not db corrupt.. but from can't find log and auto recovery, it
not seem db/log corrupt right? If so, the db will go to suspend mode?
--soonyu
"Tibor Karaszi" wrote:
> Perhaps you have auto-close turned on and some other process (like anti-virus) is opening the file?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
> >I have this error, and it auto recovery after 1 minutes.. any idea? and it
> > involved more then one db.
> >
> > Error while undoing logged operation in database 'hash'. Error at log record
> > i (20969:622890:4)..
> > Error : 9901,Severity: 21, state 1
> > the log file for database 'hash' is not available
> > Database hash cannot be open, it has been marked suspect for recovery, see
> > the sql server errorlog for more information.
> > starting up database 'hash'
> >
>|||soonyu wrote:
> ok .. i will do two thing tommrow
> 1. check got bad block
> 2. check auto-close turned on?
> 3. antivirus scan/open this file?
> but do you think auto-close will affected? auto-close you try to mentiion is
> from sql enterprise manager->database->option->auto-close?
>
That is the option she's referring to. Auto-close should never be
enabled on a production DB.
You also need to tell your antivirus software to exclude MDF, LDF, BAK,
and TRN files at minimum.