Forum Discussion
Cannot connect to AS400 via IBM DB2 database
- Anonymous9 years ago
Hi Urid1969,
Firstly, please check the IBM AS400 server status and port status as per the below steps.
a. Verify that if the IBM server is up and running following the troubleshoot steps in this article.
b. Check the port status by using “netstat” in your IBM server and verify the port is in state Listen.Secondly, choose each driver in the following screenshot when connecting to IBM database and check if it is successful. When you choose IBM, please ensure that you have IBM DB2 Data Server Driver installed on your computer (minimum requirement is the IBM Data Server Driver Package (DS Driver)). Select the driver that matches your Power BI Desktop installation (32-bit or 64-bit).
Thirdly, check if you are able to connect to IBM AS400 database from other application such as Excel.
Thanks,
Lydia Zhang
My guess is that you want to know what is the best or recommended connection in Power BI for DB2 generally.
I know that ODBC connections can potentially be slow for sometimes for large database management systems and i have read that people complain about slow speed connecting to DB2 via ODBC in Power BI (Look at post #2 in this thread).
I would recommend you using either the Microsoft or the IBM Driver instead. I had less struggle with using the this Microsoft Driver, so I am using this one. In terms of performance the Microsoft Driver seems to retrieve Data slightly slower. I tested an import with 3 Million Rows of Data from a large DB2 table. The Microsoft driver needed 2 Mins 50 Sec and the DB2 driver 2 Mins 25 Sec.
Please let me know why my IBM driver is not working. I have installed the IBM iAccess v1ri directly from the ibm website. The Microsoft driver as well as the odbc connection is working.
- Jeick6 years agoFrequent Visitor
Anonymous
What kind of error do you get when you select the IBM driver?
I described the solution to all the errors I got when I tried using the IBM driver at the last post in this thread:
- Anonymous6 years agoNot applicable
- Jeick6 years agoFrequent Visitor
Anonymous
I've seen this error when no DB2 connect license file exists in your installpath. Or when there is a version missmatch between your license file and db2 client.
Links that may help: