cancel
Showing results for 
Search instead for 
Did you mean: 

"JDBC driver not supported" after inst. of 12 client

willi_eimler
Contributor
0 Kudos

Hi Experts,

I upgraded my NW 7.3 system from ORACLE 11.2.0.4 to 12.1.0.2. After the

ORACLEupgrade, we are facing the following situation:

The J2EE system starts with ORACLE client 11.2.0.4 correctly. After

changing the ORACLE client to 12.1.0.2 we are getting the following

error in the bootstrap phase:

“JDBC driver not supported for ORACLE database”

com.sap.sql.log.OpenSQLException: Exception of type

com.sap.sql.log.OpenSQLException caught: JDBC driver not supported for

ORACLE database..

  at

com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

  at

com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

  at

com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:284)

  at

com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataSourceImpl.java:139)

  at

com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:199)

  at

com.sap.inst.jdbc.connect.JdbcCon.connectViaSecureStore(JdbcCon.java:217)

  at com.sap.inst.jdbc.connect.JdbcCon.connect(JdbcCon.java:353)

  at

com.sap.inst.jdbc.connect.TestConnect.mainIntern(TestConnect.java:78)

  at com.sap.inst.jdbc.connect.JdbcCon.main(JdbcCon.java:553)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

  at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at

com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)

Caused by: com.sap.sql.log.OpenSQLException: JDBC driver not supported

for ORACLE database.

  at

com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

  at

com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:491)

  at

com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:157)

  at

com.sap.sql.jdbc.common.CommonConnectionFactory.createCommonPooledConnection(CommonConnectionFactory.java:131)

  at

com.sap.sql.connect.factory.PooledConnectionFactory.createPooledConnection(PooledConnectionFactory.java:115)

  at

com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:38)

  at

com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:646)

  at

com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:990)

  at

com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:43)

  at

com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool.java:95)

  at com.sap.sql.connect.pool.Pool.get(Pool.java:707)

  at

com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:261)

  ... 11 more

Caused by: com.sap.sql.log.OpenSQLException: JDBC driver not supported

for ORACLE database.

  at

com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)

  at

com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:483)

  ... 21 more

Error: Couldn't connect to DB

com.sap.sql.log.OpenSQLException: Exception of type

com.sap.sql.log.OpenSQLException caught: JDBC driver not supported for ORACLE database..

Note 1914631 – “Central Technical Note for Oracle Database 12c Release

1(12.1)” quotes:

-----Start of quote of Note 1914631 -----

At the moment, for SAP products based on SAP NetWeaver 7.2x, 7.3x for

AS-JAVA and AS-ABAP+JAVA (Java Stack and Double Stack) the following

restrictions apply:

  Oracle Instant Client version 11.2.0.4 is required for SAP

installations (SWPM) of such a product, for SAP upgrades to such a

product and also for SAP system copies/system migrations of such

products.

  In order to run the SAP system with Oracle Instant Client version

12.1.0.2 you have to apply the SAP support packages from SAP note

1777021. These support packages enable the SAP system to use the Oracle

Instant Client 12.1.0.2.

-----End of quote of Note 1914631 -----

Note 1777021 – “J2EE: Introducing Support for Oracle 12” recommends the

following version of SERVERCORE in order to be able to handle ORACLE

12c:

J2EE ENGINE SERVERCORE 7.30 SP009 patch 000000

Version of component SERVERCORE of my system is:

1000.7.30.10.0.20130822221300

We are using Kernel 7.22 EXT

I installed the instantclient as recommended in note 819829 – “Oracle

Instant Client Installation and Configuration on Unix” (OCL12164.SAR)

The directory structure for client is (with links):

  /oracle/client/

  11x_64 -> /oracle/client/12x

  12x/

  instantclient -> instantclient_12102

  instantclient_12102

The environment variable LD_LIBRARY_PATH of user xxxadm contains

/oracle/client/12x/instantclient.

After installation I executed the steps of note 867976 –“Changing JDBC

driver on WEB AS Java 6.40/NW 7.0x/7.1x” (by the way, this note is not

valid to NW 7.3 and above, support has to update this note):

- In secure store of the configtool the data under tab “Connection

Pool” is:

  ClassName=oracle.jdbc.driver.OracleDriver

  url=jdbc:oracle:thin:@deabisdbci:1522:XXX

- editor mode-> cluster_config-> system-> instance-> ID5272219->

Propertysheet instance_profile

  DB_DRIVER_LOCATION=/oracle/client/12x/instantclient

- Changed the config.properties file under

/usr/sap/XXX/J52/j2ee/configtool/

  rdbms.driverLocation=/oracle/client/12x/instantclient/ojdbc6.jar

Additionally, I changed the parameter j2ee/dbdriver in the instance

profile to /oracle/client/12x/instantclient/ojdbc6.jar.

In order to force the system to make a synchronization in bootstrap

phase

I set parameter element.resynch = FORCE in file

/usr/sap/XXX/J52/j2ee/cluster/bootstrap/ bootstrap.properties.

Systemdescription:

Server contains two systems with two SIDs and two databases (result of an dualstack split)

OS: Linux GNU SLES-11 x86_64 cc4.3.4

DB: ORACLE 12.1.0.2.0

CLIENT: instant 12

J2EE servercore: SERVERCORE1000.7.30.10.0.20130822221300

Kernel: 7.22 EXT Patch 4 DBSL-Patchnr 003

I had nothing to patch to use client 12

Best regards

Willi Eimler

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Willi,

Please go through below sapnote.

2241220 - JDBC driver not supported for ORACLE database 12.1 although SAP Note 1777021 was applied

Hope this helps to solve the issue.

Regards,

Prithviraj.

willi_eimler
Contributor
0 Kudos

Hi Prithviraj,

SAP-Note 1777021 doesn' t need to be applied, because with SP10 you are able to upgrade to ORACLE 12.

By the way I forced the boot strap to resync. A resync is started everytime I start the j2ee.

I didn't patch anything on the j2ee therefore I do not have s.th. to redeploy as recommended in OSS 2241220.

Best regards

Willi Eimler

Former Member
0 Kudos

Hi Willi,

As per the note 2241220, you have completed the step 1. Force sync.

Then why not try to redeploy "the SERVERCORE.SCA should be redeployed based on the following SAP Note: 1974053" to check if that helps to overcome the issue

Regards,

Prithviraj.

willi_eimler
Contributor
0 Kudos

Hi Prithviraj,

I did this:

  1. Switch back from Instantclient 12 to 11.
  2. Start J2EE
  3. Redeploy SERVERCORE.SCA with sidadm> telnet localhost 5$$08
  4. Switch to Instantclient 12
  5. Start J2ee

Thanx for all!

former_member189780
Participant
0 Kudos

Hi Willi

I'm getting the same issue. We are on SAP Portal 7.30 and Server Core version is 12. As you mentioned that your server core version was 10. Did you upgrade server core from 10 to current one (14) or did you redeploy server core 10 again?

Pls confirm.

Thanks

willi_eimler
Contributor
0 Kudos

Hi Amarjit,

no. I didn' t rais any patch. The problem with note 2241220 is, that you have to redepoly the servercore.sca anyway, even if you have done nothing before the oracle upgrade to 12.

I redeploed patch 10 again. That solved the problem.

And do it with telnet. It is much easier than using SUM!!!

Best regards

Willi Eimler

former_member189780
Participant
0 Kudos

Thanks Willi for your reply.

One last thing to get clear.

In Our system, server core is on patch level 1000.7.30.12.0.20140727161700. Right now, current server core patch level is 1000.7.30.12.27.20140727161700.

I redeployed server core patch level 1000.7.30.12.27.20140727161700 and it crashed server. Reason was to import another core files at the same time as per oss note 1794179 - Importing AS Java Core patches for NetWeaver 7.1 or higher based products,

Now question is, if your server core was 1000.7.30.1 before the oracle cleint upgrade, then did you re-import the same patch level (1000.7.30.1)? Or did you deploy the 1000.7.30. 5 (here 5 is just my example).

Thanks

Amar

former_member189780
Participant
0 Kudos

Hi Willi,

Update: I redeployed the server core patch 1000.7.30.12.0.20140727161700 and it fixed our issue.

Thanks again for your help and reply back.

Amar


Answers (0)