Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2014
  • Last Modified:

IBM DB2 Client for Windows

Hi,
We are using IBM DB2 Client 9.5 for connecting to a DB2 server from SQL Server 2005/2008. We have created a datasource and a linked server in SQL Server for that. A query against the DB2 is working fine. But we are getting the below error after we run a query against DB2 using MSDASQL (Microsoft OLEDB provider for ODBC) provider and then run the query using IBM DB2 client.

Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "IBMDADB2.DB2COPY1" for linked server "DB2OLEDB2" reported an error. The provider reported an unexpected catastrophic failure.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "Select * from db1.user.table1" against OLE DB provider "IBMDADB2.DB2COPY1" for linked server "DB2OLEDB2".

This issue is getting resolved when we restart the SQL Server. And the issue resurfaces again when we run the query using MSDASQL provider. The MSDASQL provider always works fine but not IBM DB2 Client. Are there any compatibility issues or any other issues between MSDASQL and IBM DB2 client? Can someone please give some insight on this?
0
Srinivas_Vengala
Asked:
Srinivas_Vengala
  • 2
  • 2
1 Solution
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Hope you didn't installed OLEDB provider for DB2 from Microsoft in your machine.
Instead of MSDASQL, try using DB2OLEDB2 itself for the other one too

Kindly install this one and check it out again.

http://download.microsoft.com/download/4/4/D/44DBDE61-B385-4FC2-A67D-48053B8F9FAD/DB2OLEDB.exe
0
 
Srinivas_VengalaAuthor Commented:
We also have DB2OLEDB installed on our machine. We need to test all the drivers so that Production team can install them on the production servers. We need to have all these 3 drivers on the machine without any issues. Hence, can you tell me how can it be resolved?

And also, can you please tell me how to create a linked server to DB2 server using MSDASQL as I suspect our DB2 Linked server configuration using MSDASQL causing this issue.
0
 
Srinivas_VengalaAuthor Commented:
In particular I am looking how to configure a DSN (specifically which driver needs to be selected in ODBC administrator) which is given for the parameter  @datasrc while creating the Linked server to DB2 using MSDASQL.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Hope you meant about this one:

http://snippets.dzone.com/posts/show/3731
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now