MySQL Bugs: #29242: Catastrophic Failure, MSDASQL and Linked Server

Bug #29242	Catastrophic Failure, MSDASQL and Linked Server
Submitted:	20 Jun 2007 15:44	Modified:	28 May 2013 8:38
Reporter:	Sundar Raman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.16	OS:	Windows (Server 2003)
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	catastrophic failure, linked server, msdasql, MSSQL, oledb

Description:
(This is a re-opening of issue 28221).
When executing queries containing joins against large data sets, the following error is encountered:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "linkserv" reported an error. The provider reported an unexpected catastrophic failure.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "linkserv".

Once the error is reported, the only way to get the linked server to work again is to restart the SQL Server service.

How to repeat:
Steps to reproduce:
Create a linked server on MSSQL using the version 3.51.16 driver. Run a query that expects to receive a larger dataset (for example 10k rows), but include a join between a SQL Server table and a linked server table. For example:

select mssql.fname,mssql.lname,mssql.ssno,mssql.address1,
mysql.fname,mysql.lname,mysql.ssno
from sqlservertable mssql
join linkserv...mysqltable mysql on mysql.ssno=mssql.ssno
order by mysql.lname desc

Run the query a few times (it may work for the first 2 or 3 times). Eventually a
"catastrophic failure" is reported by the OLEDB provider.

Hi Sundar and thanks for your report.

It is not clear to me why you reported this to us instead of MS as error clearly states their provider died on their server. And suggested fix is to restart MSSQL server!

Can you please explain this to me?

Using the MSDASQL provider with any other data source (for example another SQL Server) and running a similarly large join does *not* cause the problem. 

But I understand the point. I guess my answer would be that MySQL actually responds, and there have been multiple updates to the MyODBC driver esp. when compared to Microsoft's MSDASQL releases. I'll be opening up an MSSQL report also.

Sundar, I think it's a good start.

I am not dismissing this report though until we're sure. Can you please attach following for a start:
 - ODBC trace (Data Sources (ODBC) / Tracing )
 - General query log from MySQL server from the time test starts till the error

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Cannot continue without feedback from the reporter.
The bug is closed.