The clean solution is to stick with connecting in the 'thin' mode. OCI is native code. There is a brittle relationship between the java portion of the driver and the OCI part, if/when used. Only one specific version of the java jar will work with any given version of OCI. I believe the driver guys have implemented everything in the thin mode that you can do with OCI, including referencing the tnsnames.ora file etc, so there may be no functional or performance reason to stay with OCI. However, if it's easier for you, yes, once you have a version of OCI and a driver jar that work together, as long as you get that driver to the fore in the WLS classpath, and the OCI libs in the load path, WebLogic will be able to use the driver.
Thanks for the reply.
I agree I have used only thin driver on all previous projects.
But in current project, the user authentication model is quite different and uses oracle authentication.
We are trying to use OCI only because of certain fine grained exceptions which are thrown by OCI but not on thin driver.
I would try to figure out the right drivers and version. Seems to be a time consuming task.
When I use OCI driver, and if a connection has a SqlWarning 'ORA-28002: the password will expire within 10 day'....
And when I call ............ connection.prepareCall(function); I get the java.lang.ArithmeticException: / by zero
Any solution ?