|
Problem |
If you replace the Oracle classes12.zip
with an updated version, you will need to stop and restart the WebSphere®
Application Server V4.0.3 administrative server and application servers in
order for the updated classes to be loaded. If you create a JDBC Provider
without stopping and starting, you may see a ClassNotFoundException when
you attempt to create a datasource. |
|
Cause |
Scenario: A JDBC Provider and datasource were
successfully created to connect to an Oracle application database. Later,
it was determined that the Oracle JDBC driver needed to be updated. The
datasource and JDBC Provider were removed from the administrative console
after stopping the enterprise application and application server. The old
Oracle JDBC driver (classes12.zip) was replaced with the updated version
(same name and same location). Then, in the administrative console, the
JDBC Provider was successfully recreated, but an error occurred when
attempting to create the datasource. The error in administrative console
was "IllegalArgumentException".
Looking in the tracefile we find a ClassNotFoundException on the Oracle
datasource:
[11/6/02 13:05:07:589 EST] 587c33f5 ExceptionUtil X CNTR0020E:
Non-application exception occurred while processing method
getCustomProperties on bean BeanId(admin#repository.jar#JDBCDriver,
1036532697604): java.rmi.ServerException: RemoteException occurred in
server thread; nested exception is:
java.rmi.RemoteException: ; nested exception is:
java.lang.ClassNotFoundException:
oracle.jdbc.pool.OracleConnectionPoolDataSource
java.rmi.RemoteException: ; nested exception is: |
|
Solution |
In addition to stopping and restarting
the enterprise applications and the application servers, you must also
stop and restart the administrative server to load the new JDBC driver
classes. |
|
|
|
|
|
|
|