My client is facing issue with oracle jdbc driver (ojdbc7.jar client). CA API Gateway (9.2) is throwing error "Unsupported driver class "oracle.jdbc.driver.OracleDriver".
I tried importing the jar (ojdbc7.jar) and followed instruction as mentioned in "https://docops.ca.com/ca-api-gateway/9-1/en/configure-security/tasks-menu-security-options/manage-jdbc-connections/install-the-jdbc-interface".
After following all the steps I tried testing the connection with jdbc driver class as "oracle.jdbc.driver.OracleDriver" and connection url as "jdbc:oracle:thin:@<host name>:port:<DatabaseName>".
It is throwing error: Testing Failed: JDBC URL resolved to unsupported JDBC driver class "oracle.jdbc.driver.OracleDriver" .
From the error it would appear that the permission to allow the library into the gateway is incorrect. Please provide output for:
1) ls -alt /opt/SecureSpan/Gateway/runtime/lib/ext/
2) cat /opt/SecureSpan/Gateway/node/default/etc/conf/system.properties
3) Cluster Wide Property jdbcConnection.driverClass.defaultList
Director, CA Support
Thanks for your response. Please refer to the details below for the file permissions and JdbcConnection.driverClass.defaultList.
I tried with the permissions "444" and "777" for the ojdbc7.jar but got the same error.
[root@nzlap021 ~]# ls -alt /opt/SecureSpan/Gateway/runtime/lib/ext/
drwxr-xr-x 2 layer7 layer7 4096 May 18 10:42 .
-rwxrwxrwx 1 layer7 layer7 3397734 May 18 10:41 ojdbc7.jar
-rwxrwxrwx 1 layer7 layer7 64009 Feb 22 16:13 javax.jms-api-2.0.1.jar
drwxr-xr-x 4 layer7 layer7 12288 Dec 14 15:54 ..
-rwxrwxrwx 1 layer7 layer7 385443 Apr 11 2014 tibcrypt.jar
-rwxrwxrwx 1 layer7 layer7 151866 Apr 11 2014 tibjmsadmin.jar
-rwxrwxrwx 1 layer7 layer7 15671 Apr 11 2014 tibjmsapps.jar
-rwxrwxrwx 1 layer7 layer7 392213 Apr 11 2014 tibjms.jar
-rwxrwxrwx 1 layer7 layer7 13679 Apr 11 2014 tibrvjms.jar
[root@nzlap021 ~]# cat /opt/SecureSpan/Gateway/node/default/etc/conf/system.properties
# Any properties in this file will be set as Java system properties early in the SSG startup process.
# Configuration properties for service metrics collection:
# Available properties and their default values are shown in the examples below.
# Any supplied values will be constrained by builtin limits to avoid excess
# memory and CPU usage. Age is specified in milliseconds.
# Mode for for the ping servlet.
# Choice of: OFF | REQUIRE_CREDS | OPEN | MONITOR
# Default: REQUIRE_CREDS
I've been able to duplicate the issue in our lab. I found that by downloading the driver from Oracle Database 12c Release 1 JDBC Driver Downloads and following the steps outline in the documentation that I received the error "com.l7tech.server.jdbc.JdbcConnectionPoolManager: Cannot configure a pool associated with a JDBC connection Comm due to: JDBC URL resolved to unsupported JDBC Driver class oracle.jdbc.OracleDriver". I noted that the driver class was not aligning to oracle.jdbc.driver.OracleDriver but to oracle.jdbc.OracleDriver. Once I changed all the values to "oracle.jdbc.OracleDriver" and it worked.
Thanks, changing the driver class to "oracle.jdbc.OracleDriver" worked.
I am experiencing the same issue as Rudra was seeing except that after following all of the suggestions and documentation, I am still unable to setup an Oracle 12c JDBC connection. The database information I was given by our DBA team had the JDBC URL as: jdbc:oracle:thin:@ldap://oid.inf.fedex.com:3060/FXFGTWOTK_SVC01_IDB,cn=OracleContext
Please note the use of the OID ladap. I don't know if that is an issue with my connection.
In addition, after following the directions at Install the JDBC Interface - CA API Gateway - 9.1 - CA Technologies Documentation I am still not able to see "oracle.jdbc.OracleDriver: in my drop down list within Policy Manager.
snipped from the system.properties file on gateway applicance
From reviewing your screen captures I believe the problem is that it is unable to load the class libraries as the name in the system.properties file is missing an 'r' from oracle.jdbc.OracleDriver.
i noticed that as well. When I do a CAT on the file, the "r" appears to be missing but when I do a full "VI edit" the "r" is clearly there.
I would recommend that you review the ssg.log on the gateway to see if it is complaining about a classload with stack trace. Also try restarting the gateway process just to be sure.
I have resolved this issue. Thanks so much for the feedback. I ended up moving the \noracle.jdbc.OracleDriver as the next to last item in the system.properties file. At that point, the driver started to show up in the list as available drivers.
Unrelated question: Do you know if MAG 4.1 has been released at this point?
I am going through the OTK 4.1 install document and it has a section for installing a compatibility patch to support MAG4.0. If MAG4.1 is available, I can just skip this step.
Rick Reed | Domain Architect | FXF Architecture & Delivery | FedEx Services
350 Spectrum Loop, Colorado Springs, CO | Tel: 719-484-2926 | Mobile: 719-246-3102
Glad to here that you were able to get it to work. At this point version 4.0 of MAG is the latest version.
I'm facing the same issue and tried the solution posted in this thread, but still get Testing Failed: JDBC URL resolved to unsopperted JDBC driver class "oracle.jdbc.OracleDriver".
Here is my JDBC URL: jdbc:oracle:thin:@svmilobidb01.cartasi.local:1521:ONBRDMIS
I'm not sure what else it could be but have you verified permissions and everything on the driver install file you used? Perhaps it's an odd thing like that?
I tried both:
chmod 444 ojdbc7.jar
and this is the outcome:
-r--r--r-- 1 layer7 layer7 3698857 Oct 9 11:17 ojdbc7.jar
and chmod 777 ojdbc7.jar
-rwxrwxrwx 1 layer7 layer7 3698857 Oct 9 11:17 ojdbc7.jar
but it doesn't work.
The only difference I can identify is that I'm using version 9.3 of the CA API Gateway, but I'm not sure this thing really matters.
Thank you for trying. Have you followed all the steps at Install the JDBC Interface - CA API Gateway - 9.1 - CA Technologies Documentation including the part about whitelisting the new JDBC driver? I would double-check the instructions from the documentation above to ensure everything was properly followed and nothing was missed.