OceanBase Connector/J V2.4.18

Release date: May 6, 2026 Version: V2.4.18

Version overview

JDBC V2.4.18 enhances high availability and MySQL compatibility. It introduces support for the replication mode: in scenarios where OceanBase Database is deployed in a single-node primary-standby configuration without using ODP, JDBC can automatically switch between the primary and standby nodes (failover) through the replication mode, meeting the high availability requirements of single-node deployment. It also adds support for handling Auth Switch in the changeUser interface, improving the user switching scenarios under the caching_sha2_password authentication method. Additionally, it introduces the getProceduresReturnsFunctions connection parameter to control whether the getProcedures() and getProcedureColumns() methods in the DatabaseMetaData API return metadata of functions with the same name as stored procedures. Furthermore, this version fixes multiple critical defects, further improving the driver's capabilities and overall stability.

New features

JDBC supports replication mode

In OceanBase Database 4.x distributed clusters, ODP is typically deployed, and applications connect to the cluster using the SERVICE_NAME parameter. During primary-standby failover, ODP handles the switch, and applications do not need to modify the connection string. In OceanBase Database single-node deployment, ODP is usually not deployed, and the SERVICE_NAME method cannot be used. In single-node primary-standby deployment, JDBC or other drivers are required to implement automatic primary-standby switching.

V2.4.18 introduces the replication mode: you can configure both primary and standby nodes in the URL. If the primary node fails, JDBC automatically switches to the standby node to continue providing services, achieving automatic failover and enhancing the disaster recovery capabilities of single-node primary-standby deployment.

For more information, see Replication mode (single-node primary-standby failover).

changeUser interface supports Auth Switch

When using the caching_sha2_password authentication method, the server may return an Auth Switch Request to switch the authentication plugin during user switching via the changeUser interface. In previous versions, the changeUser interface did not handle Auth Switch, leading to failed user switching under this authentication method.

V2.4.18 adds support for recognizing and handling Auth Switch messages in the changeUser interface, enabling correct authentication switching under the caching_sha2_password method and improving user switching capabilities in secure authentication scenarios.

getProceduresReturnsFunctions connection parameter

MySQL JDBC provides the getProceduresReturnsFunctions parameter to control whether the getProcedures() and getProcedureColumns() methods in DatabaseMetaData return metadata of functions with the same name as stored procedures. In previous versions of OceanBase JDBC, this parameter was missing, and by default, metadata of both stored procedures and functions were returned.

V2.4.18 introduces the URL parameter getProceduresReturnsFunctions to control whether the above-mentioned interfaces return function metadata, improving consistency with MySQL JDBC behavior.

Compatibility changes

The compatibility changes in this version mainly involve the following URL parameters.

URL parameter changes

The following URL parameters are modified:

Behavior of obStrictJdbcCompatibility

Strict compliance mode (obStrictJdbcCompatibility=true)

• Adds SQL type judgment for executeBatch and executeLargeBatch: if the SQL type is SELECT, an exception is thrown, consistent with the behavior of MySQL JDBC and Oracle JDBC.
• For executeUpdate and executeLargeUpdate: in MySQL mode, SQL type judgment is performed, and SELECT throws an exception, consistent with MySQL JDBC. In Oracle mode, no restrictions are applied, and normal execution is allowed, consistent with Oracle JDBC.
• When resultSetType is TYPE_FORWARD_ONLY, calling scrolling interfaces such as ResultSet.previous() and beforeFirst() will result in an exception, consistent with MySQL JDBC 8.

Non-strict compliance mode (obStrictJdbcCompatibility=false, default)

• Does not apply the above restrictions to executeBatch, executeLargeBatch, executeUpdate, and executeLargeUpdate, allowing normal execution.
• When resultSetType is TYPE_FORWARD_ONLY, calling scrolling interfaces such as previous() and beforeFirst() does not result in an exception.

For a detailed comparison with subsequent versions and maintenance agreements, see Behavior comparison between strict compliance mode and non-strict compliance mode in JDBC.

Bug fixes

The following are the main issues fixed in this iteration.

MySQL compatibility

• Fixed the issue where the caching_sha2_password user could not establish an SSL connection with OceanBase JDBC and returned error 23776.
• Fixed the issue where the return value of executeBatch and the behavior of BatchUpdateException were inconsistent with those of the native MySQL JDBC driver.
• Fixed the issue where the rewriteBatch syntax returned an error when the table name contained on_duplicate_key_update.
• Fixed the issue where the table comments returned by getTables were garbled when useInformationSchema=false.
• Fixed the issue where the rs.previous() method and other scrollable interface methods did not return the correct error when the result set was not scrollable.
• Fixed the issue where the return value of isAfterLast was inconsistent with that of the MySQL JDBC driver when the cursor result set was read to the end.
• Fixed the issue where the compatibility of rs.isAfterLast() was affected when the cursor result set was empty.
• Fixed the issue where the results returned by executeBatch were inconsistent when the SELECT statement used the PS protocol or the PS+ protocol.
• Fixed the issue where the Parameter at position 19999 is not set error occurred when useBatchMultiSend=true.
• Fixed the issue where an ArrayIndexOutOfBoundsException occurred when the batch insert size was close to but did not exceed maxPacketLength when rewriteBatchedStatements=true.

Oracle compatibility

• Fixed the issue where OceanBase JDBC returned an error during the conn.prepareCall("? = call PKF_NAMED.j(b=>?, a=>?, c=>?)") phase, while the native Oracle driver returned an error only during execution.
• Fixed the issue where the getObject method could not output JSON data when the JSON type was converted to BLOB in Oracle mode.
• Fixed the issue where an exception was thrown when executeBatch was called after addBatch was executed for an SQL statement without parameters using ArrayBinding.
• Fixed the issue where the The count of return parameter must be larger than 0 error occurred when the table name contained the returning keyword in the RETURNING INTO statement.
• Fixed the issue where an IndexOutOfBoundsException occurred when a stored procedure with complex expressions was called using conn.prepareCall.
• Fixed the issue where the results did not meet expectations in the PL overload scenario: when obIncludeOutOrNullParamTypeInfo was disabled during package creation and enabled during calls.

Data precision and protocols

• Fixed the issue where precision was lost in queries from Spring applications.
• Fixed the issue where the NUMBER(20) type data 18446744097622196224 was converted to 23912644608 after being written to OceanBase.
• Fixed the issue where the unknown escape sequence error occurred when executing SELECT q'[select a='#{1}']' FROM dual.
• Fixed the issue where a null pointer exception occurred when PS batch execution was performed with useOceanBaseProtocolV20=true.