Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Problem with Blobs

Author  Topic 

ejcorcoran
Starting Member

10 Posts

Posted - 2003-11-07 : 09:59:19

On Wednesday 11/05, up to a certain time, I was able to execute the following query.

select top 10 * from legacydb01.common_apps.dbo.tbl_dc16e

and get the correct results. After some time, I started getting the following error message if I tried executing it on newdb01

****************************************************************************************************************************
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' reported an error.
[OLE/DB provider returned message: Unspecified error]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetNextRows returned 0x80004005: ].
****************************************************************************************************************************


The table tbl_DC16E has a text BLOB column, which I think is creating the problem. The reasoning being that
if instead of a SELECT TOP 10 *,
I do a SELECT TOP 10 COL1,COL2,COL3,COL4 .. while omitting the text BLOB column, I do get the correct results from the query.

During the time the Query was failing in newdb01, I was able to execute the same query in newdb02 and get the correct results.

On Thursday 11/06, I tried executing the query again on newdb01 and it worked. It seems that the server had been rebooted during the evening/night.
I then tried to execute the query on newdb02 a few times. After doing it a couple of time successfully, I started getting the same error message that I was getting
on 11/05 on newdb01. ( Msg 7399 error etc.)

During the entire time, I did not have any problems in executing the same query on legacydb.

legacydb has SQL SERVER 7.0 and is a linked server on newdb01 and newdb02, both of which have SQL Server 2000.
All the queries were being executed on the SQL Query Analyzer.

Thanks and regards

X002548
Not Just a Number

15586 Posts

Posted - 2003-11-07 : 10:44:55
Is there anything in the error log? Did you do DBCC CHECKDB?

Did you try and do a trace and then try it?



Brett

8-)
Go to Top of Page

ejcorcoran
Starting Member

10 Posts

Posted - 2003-11-07 : 10:54:11
Yes we did.
There is nothing in the logs, we traced the DB and the connection. The connection returned the OLE DB error that you see above. (The same error that appears in Query Analyzer)

EJ Corcoran
Go to Top of Page
   

- Advertisement -