AnsweredAssumed Answered

CA API Gateway (9.2) fails to support oracle.jdbc.driver.OracleDriver class (oracle jdbc driver)

Question asked by Rudra_Singh on May 18, 2017
Latest reply on Oct 10, 2018 by Dustin Dauncey

Like • Show 0 Likes0
Comment • 14

Hi,

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

Please advise.

Rudra Singh

Stephen_Hughes

May 19, 2017 3:45 AM

Correct Answer

Rudra,

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.

Sincerely,

Stephen Hughes

Director, CA Support

See the reply in context

No one else had this question

Outcomes

14 Replies

Stephen_Hughes May 18, 2017 2:57 AM
Mark Correct
Correct Answer
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

Sincerely,

Stephen Hughes
Director, CA Support
1 person found this helpful
Like • Show 1 Like1
Actions
- Rudra_Singh @ Stephen_Hughes on May 19, 2017 12:23 AM
  Mark Correct
  Correct Answer
  Hi,
  
  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/
  total 4368
  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.
  #
  #com.l7tech.service.metrics.enabled=true
  #com.l7tech.service.metrics.maxFineAge=3600000
  #com.l7tech.service.metrics.maxHourlyAge=604800000
  #com.l7tech.service.metrics.maxDailyAge=31536000000
  
  # Mode for for the ping servlet.
  # Choice of: OFF | REQUIRE_CREDS | OPEN | MONITOR
  # Default: REQUIRE_CREDS
  #com.l7tech.server.pingServlet.mode=REQUIRE_CREDS
  com.l7tech.server.jdbcDriver=com.mysql.jdbc.Driver\ncom.l7tech.jdbc.mysql.MySQLDriver\ncom.l7tech.jdbc.db2.DB2Driver\ncom.l7tech.jdbc.oracle.OracleDriver\ncom.l7tech.jdbc.sqlserver.SQLServerDriver\noracle.jdbc.driver.OracleDriver
  
  "JdbcConnection.driverClass.defaultList."
  
  com.mysql.jdbc.Driver
  com.l7tech.jdbc.mysql.MySQLDriver
  com.l7tech.jdbc.db2.DB2Driver
  com.l7tech.jdbc.oracle.OracleDriver
  com.l7tech.jdbc.sqlserver.SQLServerDriver
  oracle.jdbc.driver.OracleDriver
  
  Regards,
  Rudra Singh
  Like • Show 0 Likes0
  Actions
  - Stephen_Hughes @ Rudra_Singh on May 19, 2017 3:45 AM
    Unmark Correct
    Correct Answer
    Rudra,
    
    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.
    
    Sincerely,
    
    Stephen Hughes
    Director, CA Support
    4 people found this helpful
    Like • Show 3 Likes3
    Actions
    - Rudra_Singh @ Stephen_Hughes on May 19, 2017 4:52 AM
      Mark Correct
      Correct Answer
      Hi Stephen,
      Thanks, changing the driver class to "oracle.jdbc.OracleDriver" worked.
      
      Regards,
      Rudra Singh
      Like • Show 0 Likes0
      Actions
    - rick.reed2.2 @ Stephen_Hughes on Sep 25, 2017 9:49 PM
      Mark Correct
      Correct Answer
      Stephen,
      
      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
      
      Like • Show 0 Likes0
      Actions
      - Stephen_Hughes @ rick.reed2.2 on Sep 25, 2017 10:12 PM
        Mark Correct
        Correct Answer
        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.
        
        Sincerely,
        
        Stephen Hughes
        Like • Show 1 Like1
        Actions
        rick.reed2.2 @ Stephen_Hughes on Sep 25, 2017 10:26 PM
        Mark Correct
        Correct Answer
        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.
        Like • Show 0 Likes0
        Actions
        Stephen_Hughes @ rick.reed2.2 on Sep 25, 2017 10:34 PM
        Mark Correct
        Correct Answer
        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.
        
        Sincerely,
        
        Stephen Hughes
        Director, CA Support
        Like • Show 1 Like1
        Actions
        rick.reed2.2 @ Stephen_Hughes on Sep 26, 2017 8:31 PM
        Mark Correct
        Correct Answer
        Stephen,
        
        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.
        
        Thanks.
        
        Rick Reed | Domain Architect | FXF Architecture & Delivery | FedEx Services
        350 Spectrum Loop, Colorado Springs, CO | Tel: 719-484-2926 | Mobile: 719-246-3102
        Like • Show 0 Likes0
        Actions
        Stephen_Hughes @ rick.reed2.2 on Sep 26, 2017 8:58 PM
        Mark Correct
        Correct Answer
        Rick,
        
        Glad to here that you were able to get it to work. At this point version 4.0 of MAG is the latest version.
        
        Sincerely,
        
        Stephen Hughes
        Director, CA Support
        Like • Show 0 Likes0
        Actions
r.spampinato Oct 9, 2018 2:19 PM
Mark Correct
Correct Answer
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

Any idea?
Like • Show 0 Likes0
Actions
- Dustin Dauncey @ r.spampinato on Oct 9, 2018 9:21 PM
  Mark Correct
  Correct Answer
  Hi Riccardo,
  
  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?
  Like • Show 0 Likes0
  Actions
  - r.spampinato @ Dustin Dauncey on Oct 10, 2018 8:01 AM
    Mark Correct
    Correct Answer
    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
    
    and this is the outcome:
    -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.
    Like • Show 0 Likes0
    Actions
    - Dustin Dauncey @ r.spampinato on Oct 10, 2018 9:16 PM
      Mark Correct
      Correct Answer
      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.
      Like • Show 0 Likes0
      Actions