Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    174
  • Views views
    164
  • Users 0 members are here
Related
Options

Oracle JDBC Driver Upgrade in OO 2023.05

Joao eduardo Dias mochila

Hello, experts.

We are currently using OO 2023.05 running in a RHEL 8.8. We were recently asked, by our DBA team, to upgrade our Oracle JDBC driver. However, we need assistance in identifying the correct path where the Oracle JDBC driver should be updated. We have noticed several directories within the OO installation directory that may contain JDBC driver files:
- /opt/microfocus/oo/ojdbc6.jar
- /opt/microfocus/oo/central/tomcat/lib/ojdbc6.userjdbc.jar
- /opt/microfocus/oo/central/lib/ojdbc6.userjdbc.jar
- /opt/microfocus/oo/central/var/cache/com/oracle/ojdbc7/12.1.0.2/ojdbc7-12.1.0.2.jar
- /opt/microfocus/oo/central/var/cache/com/oracle/database/jdbc/ojdbc8/19.7.0.0/ojdbc8-19.7.0.0.jar
- /opt/microfocus/oo/insights/tomcat/lib/ojdbc6.userjdbc.jar

Does anyone know which of these paths requires updating the Oracle JDBC driver?

Additionally, these files named "ojdbc6.userjdbc.jar" don't have the typical naming convention of Oracle JDBC drivers. Could anyone help us understanding if these files should also be switched when upgrading the drivers? If so, should we also change the name?

Thank you for your time and assistance.

  • Verified Answer

    +1

    Hi,

    Due to legal reasons the oracle JDBC driver was forbidden from being delivered as part of the OO installer or upgrader binaries and had to be provided at install time as a separate file. That file  was renamed when placed in oo lib folders as ojdbcX.userjdbc.jar to highlight this specific fact that it was user provided.

    Now over time internally we have upgraded the JDBC driver requirements and have documented as such for post upgrade tasks for example from 2023.05 docs see: https://docs.microfocus.com/doc/Operations_Orchestration/2023.05/UpgradeToNewVersions#Download_and_install_drivers

    Looks like in this particular case this post upgrade task has never been done and as such the installation is still using the old ojdbc6 driver.

    The main locations where driver jar change is needed are  oo/central/lib, oo/central/tomcat/lib and if using insights also oo/insights/lib, and oo/insights/tomcat/lib folders.

    The new driver does not need to have the same naming format and can keep the original oracle name without causing any issues.

    The jars from the var/cache folder are brought by OO content and should be left alone otherwise it may cause existing flows to misbehave.

    Hope this helps,

    Vlad 

  • 0 in reply to 

    Thank you for the detailed answer, Vlad!

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.