Forum Discussion
IBM DB2 Connection
Hello. I'm using Microsoft's built-in connector in Power BI to try to connect to an IBM DB2 database (for z/OS mainframe). However, I'm getting the following error message:
"Microsoft Db2 Client: The package corresponding to an SQL statement execution request was not found. SQLSTATE=51002 SQLCODE=-805".
Am I doing something wrong? Is there something specific I need to communicate to my DBA? Or is this a problem with the Power BI product? I'm using the October 2016 release of Power BI.
Thanks so much for any assistance.
I recently had to help a group of clients connect, and we found that the following conditions were necessary:
1) You must have the DB2 client installed on the machine from which you are trying to connect
2) Under Advanced Options in the Power BI connection dialog:
a) You have to use the Microsoft driver (as you mention)
b) You have to uncheck the "Navigate Using Full Hierarchy" option
3) You need to connect using the Database tab (not the Windows tab) and use your MF credentials
Without all of these in place, we had to use ODBC to connect.
FWIW, the view provided form the MF was basically just a selection of tables -- no individual columns were selectable.
20 Replies
Hi robarivas,
Do you specify specific SQL statements when connecting to IBM DB2 database? Based on my research, the above error could occur when an application is running out of resources, which is possibly due to not closing connections or improper statements. I would recommend troubleshoot the above issue following the instructions in this article and communicate to DBA to check your SQL statements .
In addition, please go to File -> Options and settings -> Options -> Diagnostics and click "enable tracing", then connect to IBM DB2 and check the detailed logs in the traces folder. Also please help to post the detailed logs here.
Thanks,
Lydia ZhangThank you for the response Anonymous. I do not specify any specific SQL statements when trying to connect to the IBM DB2 database. And I do not understand the content of the article you referred me to.
Interestingly, the connection over ODBC does actually work but performance is unusuably slow (such as when I filter a column for example).
I've emailed the log files to [email protected]
I am an administrator for DB2 on Z/OS trying to support a Power BI desk-top user having the same problem. The user sees a -805 error returned to his session, however, this error is not taking place on Z/OS. The connection was never made. I believe the package that needs to be bound is for the data provider to support the connect request. At this time we are stuck because we don't konw what package to bind.
I have the same error. I can't connect to IBM DB2 with the new version of Power BI Desktop 2.42.4611.701 32 bit (enero de 2017).
I will be possible that this new version it doesnt have some package that DB2 need to connect to?
I was reading that maybe with the IBM Data Server Driver Package this error will be fixed, but, it didn't work.
Did someone found the solution?
I tried to connect to DB2 with an old version of Power BI Desktop (september 2016) and I can connect to DB2.
So, my hipotesis is correct? The new version of PBI Desktop doesn't have the package to connect tot DB2?
Greetings - any answer to this issue? I have tried both versions (Oct 2016 and Feb 2017) and they both work. However I have a 3rd installation (2017) on a third machine that does not work. The two that work are on a 4 year old Dell latitude 64 bit Iin 7 upgraded to Win 10 and a Surface Pro 3 Win 8.1 upgraded to Win 10. both have .Net 3.5 and 4.6. The machine that does not work is a Surface Pro 4 native Win 10 also with .Net 3.5 and 4.6.
Help?
Thx - Steve
Did someone resolved this problem? I have the latest version of Power BI Desktop, but, even in this new version it doesn't work.
Finally the DBA group in my IT department did something (maybe they had to call Microsoft??) such that now the DB2 connector works...but only when you choose Microsoft as the driver option. Still doesn't work with the IBM option. But even though the DB2 connection now sorta works I can't say that I have witnessed any difference as compared to the ODBC connection I had been using previously. Anyone know what I should be looking for to see if the whole drama re: the DB2 connector had been worthwhile?
I recently had to help a group of clients connect, and we found that the following conditions were necessary:
1) You must have the DB2 client installed on the machine from which you are trying to connect
2) Under Advanced Options in the Power BI connection dialog:
a) You have to use the Microsoft driver (as you mention)
b) You have to uncheck the "Navigate Using Full Hierarchy" option
3) You need to connect using the Database tab (not the Windows tab) and use your MF credentials
Without all of these in place, we had to use ODBC to connect.
FWIW, the view provided form the MF was basically just a selection of tables -- no individual columns were selectable.
