JDBC driver compatibility assessment

Prev Next

When upgrading the Java runtime to a new major version (e.g., from OpenJDK 11 to OpenJDK 21), you must ensure that your JDBC database drivers are compatible with the new Java version. If you are keeping your current Java version, updating JDBC drivers is generally not required. This guide explains how to check compatibility and update drivers if needed.

IMPORTANT

Known issue with Microsoft SQL Server

Customers running MS SQL Server have repeatedly experienced connection errors when the JDBC driver is not updated before upgrading the JDK. If you are switching to OpenJDK 21, use mssql-jdbc-12.6.jre21.jar or later. Older versions — in particular variants with the jre11 suffix — are no longer compatible with OpenJDK 21.

Not planning a Java upgrade?

If you are staying on your current Java version, your existing JDBC drivers will generally remain compatible. The steps in this guide are not required in that case.

Requirements

  • You have an inventory of your configured database connections and the JDBC driver versions in use for each.

  • You have access to the driver directory of the Lobster Data Platform.

  • You can restart the platform.

  • You know which Java version you are upgrading to (e.g., OpenJDK 21).

Step 1 – Identify JDBC drivers in use

  1. Open the database connection configuration in the Lobster Data Platform.

  2. For each connection, note the JDBC driver (name and version, e.g., ojdbc11.jar, mssql-jdbc-12.6.jre21.jar) and the database version (e.g., Oracle 19c, PostgreSQL 16, SQL Server 2022).

Step 2 – Check compatibility with the target Java version

Consult the compatibility matrix published by each driver vendor and use the latest stable driver that supports your target Java version. The table below provides reference values for common databases when upgrading to OpenJDK 21. If you are upgrading to a different Java version, refer to the respective vendor documentation accordingly.

Database

Minimum version for OpenJDK 21

Vendor documentation

Microsoft SQL Server

mssql-jdbc-12.6.jre21.jar or later—use the jre21 ⁣variant, not the jre11.

Microsoft JDBC Support Matrix

Oracle Database

ojdbc11.jar 23.x or later.

Oracle JDBC Downloads

PostgreSQL

postgresql-42.7.x.jar or later. The current 42.7.x series is the correct product family for use with Java 21.

PostgreSQL JDBC Changelog

MySQL / MariaDB

mysql-connector-j-8.3.x.jar or later.

MySQL Connector/J versions

MariaDB (native driver)

Current MariaDB Connector/J

MariaDB Connector/J Release Notes

Salesforce (JDBC)

Salesforce JDBC driver 25.x or later requires Lobster Data Platform 26.2 or later. Earlier platform versions are not supported.

Salesforce Driver Online Help

Informix

NOTE Not supported as a hub database as of 26.2 (and patches 26.1.5 and 25.1.11). All Informix JARs have been removed from IS/lib. For other roles, provide the driver yourself and place it under IS/extlib. Test connectivity in a staging environment.

IBM Informix JDBC 4.50.JC7 Release Notes

NOTE

The driver versions listed above are reference values for an upgrade to OpenJDK 21. Always consult the official vendor documentation for your specific database and Java version combination.

Step 3 – Update drivers

IMPORTANT

Update JDBC drivers before upgrading Java. If you switch the Java version first without updating the drivers, database connections can fail and the platform may not be operational.

  1. Download the compatible JDBC driver version from the vendor's site.

  2. Replace the existing .jar file in the Lobster Data Platform driver directory.

  3. Restart the platform.

Step 4 – Test connections

  1. Open the relevant database connection in the Lobster Data Platform.

  2. Run a connection test.

  3. Check the log files for any errors or warnings related to the JDBC driver.

Best practice

Always perform driver updates and Java upgrades in a test or staging environment first before rolling out the changes to production.

Continue with: JDOM1-to-JDOM2 migration