June 24, 2009 at 9:07 am
Thanks inadvance
I got the below error message after taking the full db dump. how to avoid this.
6/24/2009 10:15:46 AM
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.
June 24, 2009 at 9:18 am
Questions: While taking the Db Dump, was your application doing any transactions into the database.
is the applicaiton or client running some set statemetns diff from the default READ COMMITTED isolation level.
??
Maninder
www.dbanation.com
June 24, 2009 at 9:30 am
I am not sure. Pleaselet us know what is Read committed isolation level
June 24, 2009 at 9:57 am
if you have admin right on SQL Server: Write
DBCC USEROPTIONS and check to see the last option, what does it say.
I bet what is happening is the SQL server might be set to default READ COMMITTED isolation level, but the appplication or client might have a SET options somewhere, which is overwritten during a transaction.
read about ISOLATION LEVELS in BOL (SQL Server books Online)
Maninder
www.dbanation.com
June 24, 2009 at 10:32 am
I ran the below statment on master DB
what can i do now. becuase i got the same alert again.
use master
go
DBCC USEROPTIONS
Results :
textsize 2147483647
language us_english
dateformatmdy
datefirst7
lock_timeout-1
quoted_identifierSET
arithabortSET
ansi_null_dflt_onSET
ansi_warningsSET
ansi_paddingSET
ansi_nullsSET
concat_null_yields_nullSET
isolation levelread committed
June 24, 2009 at 11:17 am
Where did you get these error messages/alerts? If from a log, could you provide the actual message? Perhaps even a portion of the log before and after the error?
June 24, 2009 at 11:22 am
This is error i found fron SQL log
Database backed up. Database: OperationsManager, creation date(time): 2008/12/17(13:46:51), pages dumped: 637164, first LSN: 476:1227796:1, last LSN: 477:10953:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'e:\sqldata\WSG_QA6\dump\ACX3AMA2864_WSG_QA6_OperationsManager_db_200906240110.dmp'}). This is an informational message only. No user action is required.
Error: 7886, Severity: 20, State: 2.
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.
June 24, 2009 at 12:43 pm
karthik_sql (6/24/2009)
This is error i found fron SQL logDatabase backed up. Database: OperationsManager, creation date(time): 2008/12/17(13:46:51), pages dumped: 637164, first LSN: 476:1227796:1, last LSN: 477:10953:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'e:\sqldata\WSG_QA6\dump\ACX3AMA2864_WSG_QA6_OperationsManager_db_200906240110.dmp'}). This is an informational message only. No user action is required.
Error: 7886, Severity: 20, State: 2.
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.
Based on what I am reading, and hopefully I am correct, I don't think the problem is related to your backups. It appears that those are completing okay. Is there anything to tell us what application is getting the Error: 7886 message?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply