This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: got weird cause of Websphere and DB2 Client
Feed Title: Marc's Java Blog
Feed URL: http://www.logemann.org/day/index_java.xml
Feed Description: Java related topics for all major areas. So you will see J2ME, J2SE and J2EE issues here.
you certainly know this feeling. This weird feeling when everything fails to succeed. I allways thought that it cant be so hard to get Websphere 5.1 (yes, the version with JDK 1.4 on board) running with a remote DB2 installation. It cant be hard because you have this pretty admin console for WAS, where evrything is simple.
So, i set up a JDBC provider and chose Type4 db2jcc.jar at first try. Again i thought this will get easy, because this driver doesnt need any DB2 client installation. Just a quick creation of a DataSource and here we go. Boing. Exception blablabla. Ok, i know a collegue got it working with a Type2 JDBC driver which uses IBM CLI client code, so i quickly installed the DB2 Runtime Client and configured the communication to the DB2 Server (which was awfull, but i will keep it short). Back to Websphere and another quick test for the new JDBC driver. BOING. The infamous "UnsatisfiedLinkError" Error, after googling for this, i got tons of different problems which results in this Error. Well done IBM, long live meaningful ErrorMessages.
One of the posts pointed out that perhaps Websphere or better the Type2 Driver probably cant find the native CLient libs. So a quick look in the ENV settings of Win32 told me that everything was in the PATH. Then i burnt my brain cells and was quite sure that you have to boot in order to get the modified PATH or at least stop the server process. After booting everything was ok.
Now some questions arise:
1. What the hell is IBM doing with their Error Messages. You pay tons of money for such a general bullshit message. How about "Couldnt find native library" or something?
2. When installing DB2 Runtime Client for Windows, what the hell does IBM think the installer wants to achieve? Possibly accessing a DB2, so please be so kind and tell the user that he has to reboot. That saves some debugging time.
Two hours wasted and some self questioning about the selection of my profession ;-)
Previous Topic
