Issue connecting to DB2

[Kyle Benzo]

I am able to connect to IBM Blu Lake via DB2 on my local machine but I am not able to connect to our legacy mainframe DB2. It throws the error below. I also tried connecting to a remote server to try and got the same error so I don’t think it’s an issue on my machine.

‌

does Query Xtractor assume it can collect a piece of information from the database that happens to be unavailable on our server? If so, would it be possible to wrap it in a try/except or something?

‌

Thanks,

Kyle

‌

[Cristi Scutaru]

Hi Kyle, we officially support only DB2 LUW. We never tested DB2 installed on a mainframe, so we don’t know if it works. For any other remote DB2 server, make sure you have a recent version, as the one you’ve been able to connect locally.

[Kyle Benzo]

Understood, thanks for the response. In that case, would it make more sense to add ODBC support? It would be easier to test and would extend to anything that is available via ODBC.

[Cristi Scutaru]

Please check the IBM DB2 entry from this KB page:

“The IBM.Data.DB2 driver must be installed by the user, as it is not included in our applications. You can download and install the IBM Data Server Driver Package (DS Driver) from IBM’s website. We support and we tested the LUW (Linux, Unix, and Windows) distribution, starting with version 10.5.”

We use internally an ADO.NET connection, as ODBC is rather old now.

But it looks like you already had the right Provider. Your error message looks rather DB2 version-related…