I have an error with accessing DB2 on a 64-Bit Windows platform. We had a problem with both Oracle and ODBC as well. We were able to overcome the Oracle problem by installing BOBJ in a new directory with ()'s in the path. We solved the ODBC problem by using the ODBC32 application instead of the native 64-Bit. However we still haven’t been able to resolve the DB2 driver problem. We are receiving the following error:
DBDriver failed to load: Path\dbd_db2cli.dll (The specified module could not be found.)
Thanks for the response. The drivers were indeed installed. I also searched thoroughly and my particular issue wasn’t addressed. It turns out that the install of the db2 drivers must be installed in a path without any parentheses. Similar to the problem I was having with bobj being installed in a path with parentheses. Thx!
On 64-Bit Windows the default install directory for 32-bit software is “Program Files (x86)”. I had to uninstall bobj and all my drivers and install in a directory without the parentheses. So just plain “Program Files” would suffice. Also, you must use the 32-bit ODBC client for all ODBC connections. If you use the one available from the Control Panel>Admin Tools then it’s the 64-bit client. The 32-bit client is located somewhere in the Windows directory (you may have to search for it, I forget where it is off-hand). Also make sure that you only use 32-bit drivers because BOBJ is still 32-bit software.
I think you’re still going to have to install a 32-bit driver to connect to the server. That’s what our problem was in regards to using odbc. When we set up the odic connections using the 64-bit client the dsns were unrecognized by the bobj connections, because it was reading 32-bit settings. You should still be able to connect to the database regardless as to whether it’s 32 or 64 bit since it’s all just communication via protocols.
(BOB member since 2006-08-08)