I am attempting to deploy a web module that utilizes a WebAS datasource for an external Oracle database. I expect to add a JDBC Connector leveraging the Oracle JDBC driver. I have been unable to deploy the Oracle datasource.
I receive the stack trace below whenever I attempt to Start the datasource. I find many posts asking about this error but never have I found an answer as to the cause or resolution. OSS Note 751175 describes this as a classloader problem with connectors but it does not offer any repair method that works with this problem (in my case).
I've had this problem with NetWeaver SP7 and it remains with SP10.
Does anyone have explanation? Can I expect to test such applications in NetWeaver's standalone WebAS?
ava.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4114150:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "CMR".
Thank you for your reply but unfortunately I have read these links several times and executed the instructions carefully. They do not work.
Have you tried this procedure yourself? If so could you note the exact steps you followed? Something is missing in the documentation.
There are other exceptions related to this appearing in the default trace log (see below). I believe they are the root cause but I can't pin it down.
Could you please suggest other checks I can verify?
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
... 40 more
Caused by: java.lang.ClassCastException
unfortunately it is not that easy to find out the details about this. You need to find two positions in the manuals for this. First is about JDBC Connector in the Admin manual:
This one explains how to define the JDBC datasource. But to do so you already need to have deployed the jar files. And that is done with the studio by defining and deploying a J2EE component, described here:
This should be it. According to your writing I guess you have seen the first place already. I'll take care so there will be a link to the deployment description in the future.