?
Solved

IBM DB2 Client for Windows

Posted on 2009-07-01
4
Medium Priority
?
2,051 Views
Last Modified: 2012-05-07
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
Comment
Question by:Srinivas_Vengala
  • 2
  • 2
4 Comments
 
LVL 57

Expert Comment

by:Raja Jegan R
ID: 24772846
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
 

Author Comment

by:Srinivas_Vengala
ID: 24783705
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
 

Author Comment

by:Srinivas_Vengala
ID: 24783761
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
 
LVL 57

Accepted Solution

by:
Raja Jegan R earned 1500 total points
ID: 24784302
Hope you meant about this one:

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

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are some very powerful Dynamic Management Views (DMV's) introduced with SQL 2005. The two in particular that we are going to discuss are sys.dm_db_index_usage_stats and sys.dm_db_index_operational_stats.   Recently, I was involved in a di…
When writing XML code a very difficult part is when we like to remove all the elements or attributes from the XML that have no data. I would like to share a set of recursive MSSQL stored procedures that I have made to remove those elements from …
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.
Suggested Courses

592 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question