dbimport.sh error "found unsupported JDBC Driver name: IBM Data Server Driver for JDBC and SQLJ version: 3.69.24"

[former_member186587]

Hi,

I am in process of upgrading to Sourcing/CLM 10.0 running on AIX 7.1 and DB2 10.5FP5 database.

I am at step # 5.3 Upgrade Schema & Data and trying to run "sourcing_upgrade_schema.xml" using dbimport.sh tool. WHen I start the dbimport.sh tool, I get CRITICAL error "found unsupported JDBC Driver name: IBM Data Server Driver for JDBC and SQLJ version: 3.69.24".

Error says "found unsupported JDBC Driver", but what is supported version of JDBC.

**************************************
Current Version of CLM System
**************************************
Underlying SAP System:
SAP NW 7.4 SP12
DB: DB2 10.5 FP5SAP2
Sourcing/CLM 10.0 running on DB2 10.5 FP5 database
OS Level: AIX 7100-03-05-1524
**************************************

I comfirmed my JDBC Driver installed on CLM DB & SAP DB are of same version 3.69.24:

[java 141 ]# pwd; date; unzip -p db2jcc.jar META-INF/MANIFEST.MF
/db2/CLS/db2_v105/java
Thu Mar 10 11:17:32 MST 2016
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.3
Created-By: 2.4 (IBM Corporation)
Version: 3.69.24
Class-Path: pdq.jar

[jdbc 143 ]# pwd ; date ; unzip -p db2jcc.jar META-INF/MANIFEST.MF
/sapmnt/CES/global/db6/jdbc
Thu Mar 10 11:18:07 MST 2016
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.3
Created-By: 2.4 (IBM Corporation)
Version: 3.69.24
Class-Path: pdq.jar

Bhavin

Logs for SCN.txt.zip

[former_member186587 · Accepted solution]

   After going through the SAP Note and checking instance profile parameter for my SAP NW 7.4 Portal System, it is using "db2jcc4.jar" as DB Driver. I was following below document:

Installation Guide  for "SAP Sourcing 10.0 For Deployment on SAP NetWeaver 7.31 SP10 with Database IBM DB2 for Linux, UNIX, and Windows"

Document version: 1.1 - 2015-11-18

Section # 3 Installation

Section # 3.2 & 3.3.10 are refering to use db2jcc.jar file and --> NOT db2jcc4.jar <-- file.

SAP - Please update the document accordingly.

Bhavin

I got Response from SAP as below:

This is a known issue with the drivers and the newer release of DB2. Please see Note 2119284 for instructions on how to get past this.