Error 7399 Linked Server Db2
Contents |
Reproducible Not Reproducible The product team could not reproduce this item with the description and steps provided. A more detailed explanation for the resolution of this particular item may have been provided in the comments error 7399 linked server oracle section. 2 0 Sign into vote ID 615000 Comments 17 Status Closed Workarounds 4 Type
Sql Server Error 7399 Linked Server
Bug Repros 4 Opened 10/19/2010 10:35:44 AM Access Restriction Public Description There appears to be an incompatibility with the MS OleDB for ODBC msg 7399 linked server driver method of creating linked servers and SQL 2008 R2. This method works with a SQL 2005 server. A phone call to IBM support (see info below) and numerous tests and IBM review of odbc/ibm logs revealed odd handling sql server 2005 linked server db2 of the odbc requests from SQL 2008 R2. This method still works on SQL 2005, which somewhat confirms an issue with SQL 2008 R2. Per IBM support another client recently reported SQL 2008 worked, R2 broke the functionality. DETAILS ATTACH A FILE EDIT THIS ITEM Assign To Item can only be reassigned when it is active. Comments (17) | Workarounds (4) | Attachments (0) Sign in to post a comment. Please enter a comment. Submit
Cannot Create An Instance Of Ole Db Provider "ibmdadb2" For Linked Server
Posted by smardi on 5/2/2013 at 1:12 AM /*********I, also, was struggling with this exact problem. We opened a support call with IBM who gave us a simple tip which appears to have resolved the problem - so I will share it with you.In the ODBC Data Source Administrator panel on the server, configure your linked server from System DSN.Under the Performance tab, uncheck the box 'Enable pre-fetch of data for queries'. OK, OK.Delete and re-create your linked server in SQL Management Studio.With this one change I was able to select, delete and insert records to and from our AS400 when previously only the OPENQUERY syntax would work. I hope someone else out there finds this useful!Jim**************/Thanks Jim,That worked, I was struggling with this for quite a long time.Regards,Sudhir Posted by Samuel Justin Gabay on 6/27/2012 at 12:22 PM I was having the same problem: I could not create a linked server between SQL Server 2008R2 64-bit and a DB2 for i (iSeries) 7.1 database using the MSDASQL bridge to the iSeries Access ODBC driver. I would recieve the catastrophic error when using a syntax such as:select *from SYSTEM.RDB.SYSIBM.SYSDUMMY1but it will work when using a syntax such as:select *from openquery(SYSTEM, 'select *from SYSIBM.SYSDUMMY1')Updating the SQL Server to Service Pack 2 (which as of 2012-06-27 was not officially released), but disabling the pre-fetch as Jim
here for a quick overview of the site Help Center Detailed answers to any questions cannot fetch a row from ole db provider "msdasql" for linked server you might have Meta Discuss the workings and policies of this db2 linked server sql server 2012 site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers
Sql Server Allow Inprocess
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a https://connect.microsoft.com/SQLServer/feedback/details/615000/sql-server-2008-r2-linked-server-to-db2-using-microsoft-oledb-provider-for-odbc-fail community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to add an IBM DB2 server to SQL Server's Linked Server up vote 3 down vote favorite 3 From .Net, I'm able to connect to the DB2 database: First I include a reference http://stackoverflow.com/questions/6768120/how-to-add-an-ibm-db2-server-to-sql-servers-linked-server to "IBM.Data.DB2.iSeries" Then I create a new IBM.Data.DB2.iSeries.iDB2Connection. The connection string is DataSource=ChaDb2Server;UserID=MyUsername;Password=MyPassword; Then I create an IBM.Data.DB2.iSeries.iDB2Command, and so on. Now I'm trying to get my SQL Server 2005 to access the same data directly. In SQL Server Management Studio, I right-click on Linked Servers, and select "New Linked Server..." Linked Server: ChaDb2Server Provider: IBM OLE DB Provider for DB2 Product Name: ??? Data Source: ChaDb2Server Provider String: DataSource=ChaDb2Server;UserID=MyUsername;Password=MyPassword; Location: ??? I can leave Location blank, but Product Name can't be empty and I don't know what to fill in here. On the Security tab, I select "Be made using this security context" and I repeat the UserID and password. The linked server gets created, but when I try to expand Catalogs / default / Tables, I get an error message: OLE DB provider 'IBMDADB2.DB2COPY1' reported an error. Authentication failed. (Microsoft SQL Server, Error: 7399) I have no idea where the name IBMDADB2.DB2COPY1 came from. Also, w
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2008 » SQL Server http://www.sqlservercentral.com/Forums/Topic1149829-391-1.aspx 2008 - General » Linked Server to DB2 32 posts,Page 1 of 41234»»» http://www.tech-archive.net/Archive/SQL-Server/microsoft.public.sqlserver.connect/2009-02/msg00081.html Linked Server to DB2 Rate Topic Display Mode Topic Options Author Message Koen VerbeeckKoen Verbeeck Posted Thursday, July 28, 2011 12:21 AM SSCoach Group: General Forum Members Last Login: Thursday, October 6, 2016 2:02 AM Points: 15,414, Visits: 13,137 I'm trying to create a linked server to a DB2 database on AS400. However, linked server I'm not able to run queries on the created linked server.First I tried the Microsoft OLE DB provider for ODBC, using a system DSN with the iSeries Client Access. I've created an .udl file, and I can create a successful connection.When I create the linked server with a fixed login and password, clicking on "Test Connection" yields success. However, when I browse the tables, I can only 7399 linked server see some of them not all. Querying a table that should exists results in the following error message:Msg 7399, Level 16, State 1, Line 1The OLE DB provider "MSDASQL" for linked server "LINKED_ODBC_myLinkedServer" reported an error. The provider reported an unexpected catastrophic failure.Msg 7330, Level 16, State 2, Line 1Cannot fetch a row from OLE DB provider "MSDASQL" for linked server "LINKED_ODBC_myLinkedServer".The query:select top 5 * from openquery(LINKED_ODBC_myLinkedServer,'select * from test.myTable')When I run the query a second time, it just runs forever without returning results. (and the table exists. If I go to the DB2 database with sqlexplorer, I can browse the table without a problem).So I tried a different approach. I installed the Microsoft OLE DB provider for DB2 on my machine. Again, I can create an .udl file and create a successfull connection. In SSIS, I can create a connection manager and use it without any problem. However, when I create the linked server, clicking on 'test connection' makes SSMS hang (the screen turns white). Querying the linked server with the same query as above also keeps running forever. (so it is actually worse than the ODBC linked server, although I can use it in SSIS witho
OLE DB provider must be configured to allow inprocess. Under server Objects -> Linked Servers -> Providers right click on the provider being used (IBMDASQL, IBMDA400, or IBMDARLA) and select properties. Make sure "Allow Inprocess" is checked. If the user is getting "Msg 7399, Level 16, State 1, Line 1" type errors when attempting to run the sample select statement, this is a problem with the SQL Server service and the rights the user it is running under has. There are two things that can affect this. Note that this is all Microsoft code-related and is as-is at best. Assistance with this should be directed to Microsoft service and support." If that does not give you a clue, then could you provide a script of your linked server, linked server logins, and the udl file? (You can get the linked server and linked server logins by right clicking on the linked server definition and choosing Script Linked Server As \ Create.) That might help someone understand a little better. You mentioned you do not have the Microsoft OLE DB Driver, but it is freely downloadable here: http://blogs.msdn.com/dotnetinterop/archive/2006/01/19/oledb-provider-for-db2.aspx It is part of the Feature Packs for SQL Server, all freely downloadable at these locations: http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en -- SQL Server 2005 http://www.microsoft.com/downloads/details.aspx?familyid=228de03f-3b5a-428a-923f-58a033d316e1&displaylang=en&tm#QuickInfoContainer - - SQL Server 2008 Another resource still focused on using the Microsoft OLE DB driver: http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1326266,00.html Then there are some other links that may hold some interest for you: http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=65&threadid=47240&enterthread=y Hope that something helps. RLF "Cismail via SQLMonster.com"