IBM DB2 failover connection

[AlesH]

The db2 database is currently set to fail-over switching servers in the event of an active node failure, as part of the connection, in addition to the primary node, a backup node must also be entered in the form of the command:
clientRerouteAlternateServerName=<alternative_server>;clientRerouteAlternatePortNumber=<alternative_port>;
In the case of connection definition in Power BI desktop (option "IBM Db2 Database"), "Import" mode, "IBM" or "Microsoft" Driver, when trying to enter the above parameters in the "Server" or "Database" field, it is not possible include these choices.
So what is the procedure for connecting PowerBI (version for RS) to an IBM DB2 database in a variant with active fail-over mode so that in the event of failure of the primary (and the defined server in the connection) there is a switch to an alternative server and there is no data loading error ( resource unavailable) when updating.

[AlesH]

Hi, thanks for the reply, however it doesn't solve our db2 failover and alternate server problem. So, it doesn't work. If anyone has a solution, thank you very much.

Ales

[v-rongtiep-msft]

Hi @AlesH ,

Reference:

Power Query IBM Db2 database connector - Power Query | Microsoft Learn

How to connect Power BI to IBM DB2 - Intellipaat;

Solved: Power BI Direct query connection to IBM DB2 - Microsoft Power BI Community.

And here are some conditions here that may help you later:

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. 

Solved: IBM DB2 Connection - Microsoft Power BI Community.

Best Regards

Community Support Team _ Polly

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.