JDBC Connector in NetWeaver Dev Studio WebAS

[Former Member]

Hello,

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?

Best regards,

Gary

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".

at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1836)

[Former Member]

Benny,

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?

Best regards,

Gary

Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:79)

at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)

... 40 more

Caused by: java.lang.ClassCastException

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:77)

[Benny]

Hi Gary,

I get the same error when I do not declare a new driver. Did you do that?

Can you see the new driver in the Visual Admin?

How did you proceed from there?

Regards,

Benny

[Former Member]

Hello Benny,

One of my co-workers resolved the problem which boiled down to driver configuration confusion. Here's what we learned:

• No SDA component was required though this was a good exercise for us to go through.

• The driver (JAR or ZIP) file can be added simply using the Visual Administrator JDBC Connector Runtime tab.

• We were not able to activate more than one type of datasource at a time (feature, bug or something else?)

The following configurations start okay:

**Starts***

Driver: Oracle's classes12.zip

JDBC Version: 1.x

Driver class: oracle.jdbc.driver.OracleDriver

Database URL: jdbc:oracle:thin:@host:port:instance

User&Password specified.

**Starts***

Driver: Oracle's 1.4 ojdbc14.jar

JDBC Version: 2.0

Driver class: oracle.jdbc.pool.OracleDataSourceFactory

Datasource type: ConnectionPoolDataSource

CPDS Classname: oracle.jdbc.pool.OracleConnectionPoolDataSource

Additional properties:

URL = jdbc:oracle:thin:@host:port:instance

User = xxxx

Password = yyyyy

**Will not start but the failure is expected***

Driver: Oracle's classes12.zip

JDBC Version: 1.x

Driver class: oracle.jdbc.pool.OracleConnectionPoolDataSource

Database URL: jdbc:oracle:thin:@host:port:instance

User&Password specified.

We do need to run multiple datasources using Oracle and Sybase so I'm hoping the issue we encountered is simply configuration issues again.

I appreciate your time and feedback Benny!

Best regards,

Gary

[Benny]

Hi Gary,

the only problem left seems to be that you cannot activate another datasource. However, this should be possible absolutely, as you did that already because you always have the system DS running (without it the server wouldn't deven start).

So, what happens when you try a third one?

Please also keep in mind that Sybase is not supported by SAP , that means you have to run in "vendor" mode of the driver, to not use OpenSQL (you may try out the "native" mode later to get possibly SQLTrace and Table Buffer support)

So what we need is the effects of the Sybase driver.

Regards,

Benny

[Benny]

Hi Gary,

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:

http://help.sap.com/saphelp_erp2004/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm

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:

http://help.sap.com/saphelp_erp2004/helpdata/en/9f/2ade3fc6c6ec06e10000000a1550b0/frameset.htm

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.

Regards,

Benny