=======================================================================================
New Features in the Oracle JDBC and UCP Release 23.3.0.23.09
=======================================================================================
** Mission Critical Features **
- Self-Driven Diagnosability:
This feature diagnoses the first occurrence of a failure in your Java app. It
records the critical execution state in memory and then dumps the recording on error.
- Sharding Enhancements:
UCP support for split partition set, UCP support for XA transactions,
and directory-based Sharding.
- Transparent Application Continuity (TAC) Enhancements:
Server-side templates, Draining with batches, Session-State-Stable cursor support,
and Auto-enabling on all Oracle JDBC data sources.
** Security **
- Radius Challenge-Response Authentication (2FA):
The RADIUS challenge-response authentication is an interactive authentication,
where the RADIUS server asks for a valid response to a displayed challenge.
- Support for longer passwords:
JDBC supports long passwords up to 1024 bytes, transparently without any API change.
- Kerberos Authentication Enhancements:
Kerberos authentication does not need instantiating the KerberosLoginModule or the
availability of Ticket Granting Ticket (TGT) in the CredentialCache.
** Java Performance and Scalability **
- Support for Oracle True Cache Datasource:
A True Cache instance is an in-memory, mostly diskless, fully functional, read-only
replica of the primary Oracle Database. It resides in the middle-tier, co-located
with the application and is enabled at the JDBC level by setting the new
'oracle.jdbc.useTrueCacheDriverConnection' property to true.
- DRCP (Multi-Pool & Tagging support):
The new multi-pool feature allows sub-partitioning of the DRCP between several
applications by naming the sub-partitions using (POOL_NAME= <pool_name>) in the
connect string.
- Reactive Extensions for UCP:
UCP asynchronous extension is a set of methods that extend the UCP standard to
offer asynchronous database access.
- JDBC Support for Database Pipeline (using Reactive Programming):
Pipelining is a form of network communication in which an application can send
multiple requests to a database server, without having to wait for a response.
The database sends a response when the results of each query are ready.
- Support for Data Load Mode in Reactive Streams Ingest (RSI):
The RSI allows fast data ingest into the Oracle database, using the direct path
load and Reactive Streams mechanisms. To enable the DataLoad mode, you must use the
'useDataLoadMode' method.
** Ease of Development **
- Built-in JDBC Config Providers (FileSystem, HTTPS):
Oracle JDBC supports centralized App config and resource providers through a new
extensibility or plugin mechanism based on the standard Service Provider Interface.
You can load three types of providers: Centralized Configuration Providers,
Resource Providers, and Trace Event Listener Providers.
- JSON-Relational Duality Views:
JSON-relational duality views combine the advantages of using JSON documents with
the advantages of the relational model while avoiding the limitations of each. A
JSON-relational duality view exposes data stored in relational tables as JSON documents.
- Support for BEQ in JDBC-Thin:
Bequeath protocol allows the database client (e.g., Java/JDBC application) and the
database server process residing on the same Linux host, to communicate directly
without the network layer and the network listener.
- Native Boolean datatype:
Oracle JDBC Thin driver supports the oracle.jdbc.OracleType.BOOLEAN data type in
compliance with the ISO SQL standard.
=======================================================================================
Important behavior changes in Oracle JDBC 23c
=======================================================================================
- setBoolean(int parameterIndex, boolean x):
Starting from Oracle Database 23c, the JDBC-thin driver supports the BOOLEAN
SQL data type newly introduced in 23c Oracle database. When you call setBoolean()
method, the driver will send the value as a native BOOLEAN value as opposed to a
VARNUM(1/0) like in the previous releases. This might cause some incompatibility
issues in your current code. You can handle this by changing your code to either
a) change the parameter datatype of setBoolean() to a oracle.jdbc.OracleType.BOOLEAN
or b) call setInt instead of setBoolean.
- JDBC Logging:
Starting from Oracle Database 23c, diagnose-on-first-failure is ON by default.
This means that it records the critical execution state in memory, and then dumps
the recording on error. When you have the JDBC logging enabled, you may notice
an increased number of logs because of this feature. You can disable this feature
via -Doracle.jdbc.diagnostic.enableDiagnoseFirstFailure=false or using the
DiagnosticMBeans interface.
- ojdbcx_g.jar, ojdcxdms_g.jar, and dms.jar files are no longer required:
Starting with Oracle JDBC 23c, the diagnosability is simplified and eliminates
the need to switch to debug jar files. The enhanced diagnosability works with
ojdbc8.jar or ojdbc11.jar in the class path for all usecases
(production, debug, metrics) and it does not require any of the additional debug
jars ojdbc8_g.jar, ojdbc8dms.jar, ojdbc8dms_g.jar, ojdbc11_g.jar, ojdbc11dms.jar,
ojdbc11dms_g.jar, and dms.jar. Therefore, we do not ship these debug jars from 23c.
- osdt_cert.jar and osdt_core.jar are not required:
Starting with Oracle Database 23c, oraclepki.jar has been redesigned and
no longer requires the extra osdt_core.jar and osdt_cert.jar.
=======================================================================================
Deprecation or De-support notices in Oracle JDBC 23c
=======================================================================================
- Deprecation of Oracle JDBC-OCI driver or Type 2 Client Driver:
Most of the Java applications (99%) use Oracle JDBC Thin driver. Since, JDBC-OCI
driver aka thick JDBC driver is no longer used by customers, we will be
de-supporting JDBC-OCI or Type 2 client driver starting from Oracle DB 24c release.
- De-support of oracle.jdbc.rowset:
Starting with Oracle JDBC 23c, the oracle.jdbc.rowset package will no longer
be supported (the code has been removed).
=======================================================================================
References and Resources
=======================================================================================
JDBC and UCP Landing Page - www.oracle.com/jdbc
Changes in this release for Oracle JDBC dev guide - https://docs.oracle.com/en/database/oracle/oracle-database/23/jjdbc/changes-this-release-oracle-database-jdbc-developers-guide.html#GUID-7800B599-D924-4284-ADEC-10E468842BD0
What’s in Oracle Database 23c for Java Developers? (technical brief)-
https://www.oracle.com/a/tech/docs/database/whats-in-oracledb23c-for-java-developers.pdf
JDBC and UCP Downloads Page - https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html
JDBC, UCP, OJVM, and Open Source Projects Timeline -https://www.oracle.com/a/tech/docs/database/jdbc-ucp-ojvm-timeline.pdf
Github location for Oracle Extensions - https://github.com/oracle-samples/ojdbc-extensions
Oracle R2DBC - https://github.com/oracle/oracle-r2dbc
=======================================================================================
Known Problems Fixed in the Patch Release 23.3.0.23.09
=======================================================================================
Bug 35641252 - TEST BUG: CREATING TABLE CONTAINS XMLTYPE/BFILE FAILED WITH ORA-43853
Bug 35627364 - [OPENLDAP] NPE WHEN OPENLDAP+TLS IS USED
Bug 35588441 - TEQ: INTERMITTENTLY NOT ABLE TO RECEIVE NOTIFICATION FOR NULL XMLTYPE PAYLOAD
Bug 35475639 - JAVADOC: INCORRECT PREFIX FOR DIAGNOSTIC PROPERTIES IN JAVADOC IN ORACLEDRIVER.JAVA
Bug 35403229 - PREPAREDSTATEMENT.GETPARAMETERMETADATA() FAILED WITH ORA-18734
Bug 35365030 - JDK11: KPRB: PARSING XML TYPE FAILED WITH ORA-31011
Bug 35360651 - DRCP: OPEN CURSORS SHOULD BE CLEANED UP AFTER IMPLICIT RELEASE
Bug 34605867 - PUBLISHER.SUBSCRIBE() REPORTS NOSUCHELEMENTEXCEPTION AND TIMEOUTEXCEPTION
Bug 34396647 - ADDING SUBSCRIBER TO A PUBLISHED CONNECTION OBJECT FAILS WITH ORA-01017
Bug 34124974 - AYSNC TEST RUNS FOR MORE THAN AN HOUR UNTIL 'NO SPACE LEFT ON DEVICE' WHEN LOGGING ENABLED
Bug 34120266 - COMPLETABLEFUTURE.THENACCEPT() HANDS WHEN CONNECTION TO SHARED MODE DATABASE
Bug 33627888 - ORACLECALLABLESTATEMENT.EXECUTEASYNCORACLE FAILING IN MULTITHREADED ENVIRONIMENT
Bug 33586838 - WHEN MULTIPLE THREADS EXECUTINGRSET.PUBLISHERORACLE, INTERNALLY FORK JOIN POOL THREADS TAKING TIME TO READ DATA FROM BLOB
Bug 33570676 - DEADLOCK WHEN MULTIPLE THREADS READING BFILE
Bug 35043233 - JDBC-STRESS: BOOLEAN DATATYPE SUPPORT FOR SETOBJECT API
Bug 34242298 - CALLING PROCEDURE CONTAINS BOOLEAN TYPE FAILS WITH ORA-01460
Bug 34877464 - 23cBETA: Oracle Sharding DB: In WebLogic, UCP XA connection are reporting "UCP-45064: All connections in the Universal Connection Pool are in use"