Forum Discussion
IBM DB2 Connection
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.
My solution was to update to latest version of BI (stated earlier so sorry nothing new). It is now working on four different pieces of hardware (laptops and a Surface Pro 4). What version are you running and what OS?
Update: I'm now getting the following error when I use the IBM driver:
"IBM DB2: ERROR [08001] [IBM] SQL30081N A communication error has been detected. Communication protocol being used: "SSL". Communication API being used: "SOCKETS". Location where the error was detected: "SOCKETS". Communication function detecting the error: "sqlccSSLSocketSetup". Protocol specific error code(s): "410", "", "". SQLSTATE=08001"
At a minimum I'd desperately like to know which of the following I need to focus my attention on to fix this: my company's DBA group, local machine (i.e., software set-up/configurtion issues), or Microsoft's Power BI team (maybe a connector flaw?).