cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC Driver: Unable to locate a suitable JDBC driver to establish a connect

Former Member
0 Kudos

Dear all,

We have deployed the JDBC driver for DB2 Z/OS in the PI 7.10 adapter.

This driver was downloaded from SAP swdc, release 9.1 FP8, and deployed succesfully according to OSS note 1138877.

Now we have configured a JDBC connection to a DB2 database with the

following parameters:

JDBC Driver: com.ibm.db2.jcc.DB2Driver

Connection: jdbc:db2//myserver.com:32993/DS81

User: NICONUSER

Password: XXXXXXX

When we try to test this connection the following message is returned bythe system:

"com.sap.engine.interfaces.messaging.api.exception.MessagingException:

Error when attempting to get processing resources:

com.sap.aii.af.lib.util.concurrent.ResourcePoolException: Unable to

create new pooled resource: DriverManagerException: Unable to locate a

suitable JDBC driver to establish a connection:"

I tried to test the connection via java executing this command from the

OS level:

/opt/IBMJava2-s390x-142/bin/java com.ibm.db2.jcc.DB2Driver -url

"jdbc:db2://myserver.comi:32993/DS81" -user NICONUSER -password XXXXXX

And the message returned is:

"There is no main method in class: com.ibm.db2.jcc.DB2Driver"

Of course in this last test I'm using the java version installed at OS

level, but it should work anyway, I guess.

We have tried to use the JDBC testing tool described in OSS note 1085539.

However, the application comes in a .ear file which must be converted toa .sda file in order to be deployed with JSPM. Unfortunately we don't have a clear idea about how to carry out this conversion.

We'd appreciate any suggestions, ideas or even a suitable sda file for the test tool!

Thank you very much in advance.

Francisco Martínez

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

The problem has been solved. it was really a stupid issue.

We were using this connection: jdbc:db2//myserver.com:32993/DS81

and the right one is jdbc:db2://myserver.com:32993/DS81

(please observe the ":" before the double slash)

The problem was caused by a sintax error in this IBM page:

http://www.ibm.com/developerworks/data/library/techarticle/dm-0512kokkat/

Problem solved.

Regards

Francisco

Former Member
0 Kudos

We managed to install de JDBC connection test tool provided by SAP in OSS note 1085539.

The problem still remains and the tool returns this error message:

Exception Occurred : No suitable driver

----


Exception Stack Trace : java.sql.SQLException: No suitable driver

+ at java.sql.DriverManager.getConnection(DriverManager.java:545)+

+ at java.sql.DriverManager.getConnection(DriverManager.java:171)+

+ at com.sap.util.TestJDBCUtil.testDriverManagerConnect(TestJDBCUtil.java:52)+

+ at com.sap.tests.TestJDBCConnectionServlet.processRequest(TestJDBCConnectionServlet.java:41)+

+ at com.sap.tests.TestJDBCConnectionServlet.doPost(TestJDBCConnectionServlet.java:74)+

+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)+

+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)+

+ at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)+

+ at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)+

+ at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:438)+

+ at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)+

+ at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:402)+

+ at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:391)+

+ at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:93)+

+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)+

+ at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:188)+

+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)+

+ at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)+

+ at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+

+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)+

+ at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)+

+ at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+

+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)+

+ at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)+

+ at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+

+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)+

+ at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)+

+ at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+

+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)+

+ at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)+

+ at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)+

+ at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)+

+ at java.security.AccessController.doPrivileged(Native Method)+

+ at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)+

+ at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:250)+

----


By the way, if someone needs this test tool in sda format please let me know and I'll send it to her/him.

Thanks and Regards

Francisco

Former Member
0 Kudos

Hi Mr.

Did you correctly configured the provider.xml descriptor file, adding <jar-name> tag referred to the jdbc driver?

Former Member
0 Kudos

Hi,

Check JDBC Drivers are not installed properly.

You have to configure ojdbc14.jar fille

please follow the pdf

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60237e74-ef19-2b10-5a9b-b35cc6a2...

Check similar discussions here:

and have a look at this guide and cross check the steps you have performed.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4...

i hope it will help you.

regards,

ganesh.

Former Member
0 Kudos

Dear Ganesh and Spantaleoni,

Thanks for your responses.

However, as I wrote above, we are dealing with a PI 7.10 so the guide does not apply here.

The deployment of the JDBC driver was succesful so it is not a installation issue. At least I have done what SAP Support says what is to be done.

In fact, I can test DB2Binder with no errors. The problem appears in the communication channel monitoring.

Regards

Francisco

Former Member
0 Kudos

Hi Francisco,

Maybe this note is applicable for your problem in your environment:

Note 1255525 - DB2-z/OS: jdbc V9.1 driver not using defined hostname

Cheers,

Diego.