Had some problems this morning migrating an application from the Oracle 10.2.01 driver to the 10.2.03 driver on Windows. You would think this would be seamless transition, but of course not. Went ahead and backed out .01 and removed it from the file system (remember to stop any and all applications touching the Oracle driver [COM+, WebSphere, etc]). Kicked up the .03 installer and completed the install. Started the application, then noticed the following in the log file:
java.lang.UnsatisfiedLinkError: no ocijdbc10 in java.library.path
Here was the problem: The .01 client installed to d:\oracle and the .03 client installed to d:\oracle\ora102. Since this value is written to the system PATH, java apparently will not see the update until the system is rebooted. Prior to the reboot, java was using the .01 location to find the thick driver when it was actually in d:\oracle\ora102. So, if you run in to this problem, reboot the server and see if that fixes the issue.
The alternative solution is to simply use the Thin driver :’)
java.lang.UnsatisfiedLinkError: no ocijdbc10 in java.library.path
Here was the problem: The .01 client installed to d:\oracle and the .03 client installed to d:\oracle\ora102. Since this value is written to the system PATH, java apparently will not see the update until the system is rebooted. Prior to the reboot, java was using the .01 location to find the thick driver when it was actually in d:\oracle\ora102. So, if you run in to this problem, reboot the server and see if that fixes the issue.
The alternative solution is to simply use the Thin driver :’)
No comments:
Post a Comment