This content has been marked as final. Show 6 replies
Make sure the oracle JDBC driver version you have (if any) in your client environment
matches the version used by WebLogic.
Thanks for your reply.
I am not using any JDBC Driver in my client program. All are configured in WLS10.3.
I am only using configured JNDI name in my program to get Datasource.
Make sure to keep the required jdbc driver into the preclasspath.
That should solve your problem.
Hi, sorry Kal, that is already taken care of, else WLS couldn't have produced the connection already.
So, Hari, your application is a standalone java program, and you are going to have to double-check that
the application environment has no weblogic or driver classes in it's class path that are of any different
version than the WebLogic server you are talking to.
yes. my application is a standalone application and I'm having the below list of jar files in my classpath:
get rid of
from the runtime client classpath.