While starting the server I got this error. The db2profile is set in the .profile in the server.
I installed the application(ear file) successfully in the WAS 6.0. After the installing the application I tried to stop and start the server then I am getting this error.
*************Error found on SystemOut.log*****************
Caused by: java.sql.SQLException: java.lang.UnsatisfiedLinkError: Can't find library db2jdbc (libdb2jdbc.so or .so) in sun.boot.library.path or java.library.path
sun.boot.library.path=/usr/IBM/WebSphere/AppServer/java/jre/bin
java.library.path=/usr/IBM/WebSphere/AppServer/java/jre/bin:/usr/IBM/WebSphere/AppServer/java/jre/bin/classic:/usr/IBM/WebSphere/AppServer/java/jre/bin:/usr/IBM/WebSphere/AppServer/bin:/usr/mqm/java/lib:/usr/opt/wemps/lib:/home/opicmdb2/sqllib/lib32:/home/opicmdb2/sqllib/bin:/usr/lib:/home/opicmdb2/sqllib/java
at COM.ibm.db2.jdbc.app.DB2Driver.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java(Compiled Code))
at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code))
at java.lang.Class.newInstance3(Class.java(Compiled Code))
at java.lang.Class.newInstance(Class.java(Compiled Code))
The problem appears to be that you're using a 64-bit WAS JVM and pointing to the 32 bit DB2 libraries.
Java version = J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142ifx-20070604 (ifix 120916 : 142_SR8 + 119825) (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
It should be pointing to sqllib/lib instead of sqllib/lib32. What I would recommend you try is the following:
1. Edit db2profile and find where it's setting the libpath to lib32
2. Change this to point to lib
3. Do this for any other location in this db2profile file that I'm neglecting. I believe it's just LIBPATH.
4. Source the db2profile again so it's got the right settings
5. Restart server1
Alternatively, you could set up your application to use Type 4 DB2 drivers and avoid this issue altogether.
Hope that helps!
~HT
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM
Ok, thanks for sending. The paths are set correctly so the next question would be does this path actually exist on the server:
/home/opicmdb2/sqllib/lib/libdb2jdbc.so
Also, this is a WebSphere Portal forum. You do not appear to have WebSphere Portal installed at all. You might have better luck posting this on a WAS or DB2 forum.
~HT
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM
Tags
Use the search field to
find all types of content in My developerWorks with that tag.
Use the slider bar to see more or fewer tags.
Popular tags shows the top tags for this particular type of content or application that you're viewing.
My tags shows your tags for this particular type of content or application that
you're viewing.