I've been using the "Oracle Thin Driver", and I've been using the jar in
the WebLogic 8.1SP4 distribution at
"$WEBLOGIC_HOME/server/ext/jdbc/oracle/920/ojdbc14.jar", and a class
name of "oracle.jdbc.driver.OracleDriver". This has been working fine.
I recently upgraded the WebLogic distro on my box to 8.1SP6, and
suddenly this connection from SQuirreL stopped working. I tried
changing the jar file to use to the one from WLS 9.2, and then this
worked again.
Before I file a support case with BEA for this problem, I want to
understand more aspects of this, at least from the scope of SQuirreL.
During this upgrade to SP6, I was also working on an app running in
WebLogic. I hadn't tested the database code in the app before I
upgraded to SP6. When I finally got to testing the database code, I
found that it was failing to connect for an unknown reason.
After I downgraded the WebLogic instance back to SP4, both my SQuirreL
connection (using the original jar file) and my database code suddenly
started working.
Along the way, I also noticed that my connection pool in WebLogic wasn't
even using that driver class name. It was using
"weblogic.jdbc.oracle.OracleDriver", which I later found in
"$WEBLOGIC_HOME/server/lib/wloracle.jar".
So, first of all, what driver should I be using in SQuirreL, and from
what jar file should I get it?
Secondly, could anyone shine any light on the issues I'm seeing here?
|