OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Connector/J

V2.4.19
  • What is OceanBase Connector J?
    • Overview of OceanBase Connector/J
    • Compatibility requirements
  • Install Driver
    • Install and load OceanBase Connector/J
  • Instructions
    • Quick start
      • Import packages
      • Establish a database connection
      • Create a Statement object
      • Run queries and retrieve ResultSet objects
      • Process ResultSet objects
      • Close ResultSet and Statement objects
      • Manage tables and data
      • Commit changes
      • Close a database connection
      • Examples
    • Data sources and URL
      • Data source overview
      • Database URL
      • clientInfoProvider
    • Java data streams
      • Overview of Java data streams
      • LONG and LONG RAW data types
      • Use LOBs
        • Overview of LOB data types
        • LOB data interface
        • LOB locator interface
      • CHAR, VARCHAR, and RAW data types
    • Statement caching
      • Overview of statement caching
      • Use statement caching
      • Reuse statement objects
    • Call a stored procedure
    • Handle SQL exceptions
    • Result set
      • Overview of result sets
      • Limitations
      • FetchSize
      • refreshRow
      • useCursorFetch
    • Batch processing
    • Failover and Load-Balancing
      • Failover and load balancing modes
      • LoadBalance strategies
      • Load balancing strategy configuration methods
      • Replication mode
    • Rich client
    • Logging
    • Network overheads
    • Show Trace
    • Security features
    • Troubleshooting
  • Reference
    • Features specific to the Oracle mode
      • Binary Protocol (Prepared Statements)
        • COM_STMT_PREPARE_EXECUTE
        • COM_STMT_SEND_PIECE_DATA
      • Call PL stored procedures
      • Scrollability of a result set
      • Use ARRAY and STRUCT classes
      • Distributed transactions
        • Overview
        • XA components
        • Distributed transaction examples
      • Obtain remarks
      • Data types supported in Oracle mode
      • Error messages in Oracle mode
    • Supported SQL and PL data types
    • Common APIs
      • Overview
      • java.sql.Connection
      • java.sql.CallableStatement
      • java.sql.DatabaseMetaData
      • java.sql.Driver
      • java.sql.PreparedStatement
      • java.sql.ParameterMetaData
      • java.sql.ResultSet
      • java.sql.ResultSetMetaData
      • java.sql.Statement
      • javax.sql.ConnectionPoolDataSource
      • javax.naming.Context
      • javax.sql.PooledConnection
      • com.oceanbase.jdbc.ObPrepareStatement
    • Behavior differences between JDBC strict compatibility mode and non-strict compatibility mode
  • Release Notes
    • V2.4
      • OceanBase Connector/J V2.4.19
      • OceanBase Connector/J V2.4.18
      • OceanBase Connector/J V2.4.17
      • OceanBase Connector/J V2.4.16
      • OceanBase Connector/J V2.4.15
      • OceanBase Connector/J V2.4.14
      • OceanBase Connector/J V2.4.13
      • OceanBase Connector/J V2.4.12
      • OceanBase Connector/J V2.4.11
      • OceanBase Connector/J V2.4.8
      • OceanBase Connector/J V2.4.5
      • OceanBase Connector/J V2.4.4
      • OceanBase Connector/J V2.4.3
      • OceanBase Connector/J V2.4.2
      • OceanBase Connector/J V2.4.1
      • OceanBase Connector/J V2.4.0
    • V2.2
      • OceanBase Connector/J V2.2.11
      • OceanBase Connector/J V2.2.10
      • OceanBase Connector/J V2.2.7
      • OceanBase Connector/J V2.2.6
      • OceanBase Connector/J V2.2.3
      • OceanBase Connector/J V2.2.0

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Connector/J
  3. V2.4.19

OceanBase Connector/J V2.4.16

Last Updated:2026-09-17 02:32:36

Overview
New features
Compatibility changes
Product behavior changes
URL parameter changes
Bug fixes

Release date: October 15, 2025 Version: V2.4.16

Overview

JDBC V2.4.16 optimizes the call logic of PL statements, rewriting {call xxx} into anonymous blocks in the form of begin...end to enhance Oracle compatibility. It adds the capability to validate the sequence numbers of protocol packets, intercepting data correctness issues. It also introduces logic to send the data types of out and null parameters in procedures to OBServer, addressing scenarios with duplicate procedure names. This resolves the issue where executing PL statements in overloaded procedures results in exceptions when retrieving result sets, improving stability. Additionally, it optimizes the performance of getString and getcolumnname.

New features

  • Enhanced Oracle compatibility by rewriting {call xxx} statements into anonymous blocks in the form of begin...end.
  • Added the capability to validate the sequence numbers of protocol packets, preventing data correctness issues.
  • Introduced logic to send the data types of out and null parameters in procedures to OBServer, addressing scenarios with duplicate procedure names.

Compatibility changes

Product behavior changes

When autoReconnect=true, there is a risk of data correctness issues. Therefore, starting from V2.4.16, the autoReconnect=true configuration is disabled. Setting autoReconnect=true will result in an error, and only autoReconnect=false or omitting the setting (using the default value false) is allowed.

URL parameter changes

The following URL parameters are added:

Option name
Status
Default value
Description
obConvertCallsToBlocks New false For Oracle tenants, whether to convert {call xxx} statements into anonymous blocks in the form of begin...end.
obIncludeOutOrNullParamTypeInfo New false For Oracle tenants, whether to send the data types of out and null parameters in procedures to OBServer, typically used to handle scenarios with duplicate procedure names.

Bug fixes

The main issues fixed in this iteration are as follows:

  • Fixed the issue where getSubString returns a CLOB field, and the OBServer returns an incorrect field length, causing truncation.
  • Fixed the issue where, when cacheCallableStmts is enabled, concurrent reads of CLOB data after conn.close cause confusion.
  • Fixed the issue where, in the PS protocol, when arraybinding execution fails, the PS does not close promptly, leading to an excessive number of PS cursors.
  • Fixed the issue where, when sending piece data to write BLOB data fails, calling ps.close() does not successfully close the PS, leading to an excessive number of PS cursors.
  • Fixed the issue where, when rewriteBatchedStatements=true, the getGeneratedKeys method is incorrect when an insert on duplicate key statement contains \n.
  • Optimized the performance of retrieving the corresponding result set index by column name in the MyBatis framework.
  • Fixed the issue where, when a procedure is overloaded, executing PL statements to retrieve result sets results in exceptions.
  • Fixed the issue where, when executing the Execute method, JDBC does not check whether the SQL statement bound to the statement has been rewritten, directly using the rewritten SQL statement's parameter information, leading to a program error-4016 Internal error.
  • Fixed the issue where, for case-sensitive tenants, JDBC fails to retrieve PL parameter information using uppercase parameters, leading to PL call errors.
  • Fixed the issue where, when the order of out parameters called by the user does not match the defined out parameters, the correct parameters cannot be matched.

Previous topic

OceanBase Connector/J V2.4.17
Last

Next topic

OceanBase Connector/J V2.4.15
Next
on this page
Overview
New features
Compatibility changes
Product behavior changes
URL parameter changes
Bug fixes