An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.
For a list a list of issues resolved since general availability, refer to the fixes.
Certified with Oracle 21c R1 (21.1)* Driver version 6.0.0.000392 (F001326.U000671)
Certified with Oracle 19c R1 (19.1)* Driver version 6.0.0.000032 (F000211.U000122)
Certified with OpenJDK 11.* Driver version 6.0.0.000006 (F000174.U000090).
Certified with OpenJDK 8 on Windows and Linux.* Driver version 6.0.0.000006 (F000174.U000090).
Certified with Oracle JDK 11.
Certified with Oracle 18c (18.3).
Certified with Oracle 18c R1 (18.1).
The installer program has been enhanced to support Azul Zulu JRE 11. As a result of this change, the installer has ended support for some of the old operating systems. The installer supports the following operating systems after the enhancement:*
Any operating system on a machine using a JRE that is Java SE 8 or higher (LTS version), including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
Windows 8.1 or higher
Windows Server 2012 RC2 or higher
Important: These changes do not affect the operating system requirements of the driver.
The driver has been enhanced to use proxy server settings defined in the JVM system properties by default. If no proxy settings are defined in the connection string or data source, the driver will attempt to use the values of the http.proxyHost and
http.proxyPort JVM system properties to connect to the database.*
The driver has been enhanced to support Windows Defender Credential Guard when using Kerberos Authentication.*
The driver has been enhanced to include timestamp in the Spy and JDBC packet logs by default. If required, you can disable the timestamp logging by specifying the following at connection: For Spy logs, set spyAttributes=(log=(file)Spy.log;timestamp=no)
and for JDBC packet logs, set ddtdbg.ProtocolTraceShowTime=false.*
Interactive SQL for JDBC (JDBCISQL) is now installed with the product. JDBCISQL is a command-line interface that supports connecting your driver to a data source, executing SQL statements and retrieving results in a terminal. This
tool provides a method to quickly test your drivers in an environment that does not support GUIs.*
The driver has been enhanced to support using connection information stored in an LDAP entry to establish a connection. You can configure the driver to use LDAP with the new LDAPDistinguishedName property and refreshed ServerName and PortNumber properties.
The driver has been enhanced to support connecting through Oracle Connection Manager using the TNSNAMES.ORA file.*
The BatchMechanism connection property has been added to the driver. It determines the mechanism that is used for executing batch operations. It's a flexible replacement for BatchPerformanceWorkaround property. Therefore, if you use
BatchPerformanceWorkaround for specifying the batch mechanism instead of BatchMechanism, the driver will allow it. If you use both BatchMechanism and BatchPerformanceWorkaround simultaneously, BatchMechanism will take precedence over BatchPerformanceWorkaround.
The driver has been enhanced to support Kerberos constrained delegation. Constrained delegation is a Kerberos mechanism that allows a client application to delegate authentication to a second service.
The GSSCredential connection property has been added to the driver. It specifies the GSS credential object used to instantiate Kerberos constrained delegation.
The driver has been enhanced to support returning implicit result sets from stored procedures.
The driver has been enhanced to use Oracle Internet Directory as a means to store authentication information.
The driver has been enhanced to support Oracle Wallet SSL authentication introduced in Oracle 126.96.36.199. The AuthenticationMethod connection property should be set to either SSL or SSLUIDPassword to allow SSL authentication when connecting
with the driver.
Support for Oracle Database Vault.
Support for Oracle Database Exadata Cloud Service.
The driver has been enhanced to support the following new data integrity algorithms for Oracle Advanced Security on Oracle 12c and higher:
The maximum supported length of identifiers has been increased to 128 bytes when connecting to Oracle 12c R2 (12.2) databases. This change has been implemented to reflect the new maximum length supported by the server.
The driver has been enhanced to support the extended data types. When the Oracle server is configured with MAX_STRING_SIZE=EXTENDED, the driver supports the following maximum string sizes:
NVARCHAR2: 32766 bytes
RAW: 32767 bytes
VARCHAR2: 32767 byte
The LOBPrefetchSize connection property has been added to the driver and is supported for Oracle database versions 188.8.131.52 and higher. This connection property allows you to specify the size of prefetch data the driver returns for BLOBs
and CLOBs. With LOB prefetch enabled, the driver can return LOB meta-data and the beginning of LOB data along with the LOB locator during a fetch operation. This can have significant performance impact, especially for small LOBs which
can potentially be entirely prefetched, because the data is available without having to go through the LOB protocol.
The default value for the SDUSize property has been updated to 16384.
The default value for the EncryptionLevel property has been updated to accepted.
The default value for the DataIntegrityLevel property has been updated to accepted.
The driver no longer sets the java.security.krb5.conf system property to force the use of the krb5.conf file installed with the driver jar files in the /lib directory of the product installation directory.
Added the RegisterStatementPoolMonitorMBean connection property. Note that the driver no longer registers the Statement Pool Monitor as a JMX MBean by default. You must set RegisterStatementPoolMonitorMBean to true to register the Statement Pool Monitor and manage statement pooling with standard JMX API calls.
Certified with OpenJDK 11.* Driver version 5.1.4.000466 (F000381.U000186).
Certified with OpenJDK 8 on Windows and Linux.* Driver version 5.1.4.000466 (F000381.U000186).
Certified with Oracle JDK 11.* Driver version 5.1.4.000466 (F000381.U000186).
Certified with Oracle 12c R2 (12.2). Driver version 5.1.4.000391 (F000327.U000148).
The SDUSize connection property has been added to the driver. This connection property allows you to specify the size in bytes of the Session Data Unit (SDU) that the driver requests when connecting to the server.
The SupportBinaryXML connection property has been added to the driver. This connection property enables the driver to support XMLType with binary storage on servers running Oracle 12C and higher.
The connection properties RandomGenerator and SecureRandomAlgorithm have been added to the driver.
RandomGenerator allows you to specify the type of random number generator (RNG) the database uses for secure seeding.
SecureRandomAlgorithm can be used to specify the SecureRandom number generation algorithm used for secure seeding with implementations of JDK 8 or higher when RandomGenerator is set to secureRandom.
The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
Certified with Oracle 12c
Enhanced to support all Oracle 11gR2 Kerberos encryption algorithms
Enhanced to throw warning when EnableBulkLoad fails
Added support for Oracle Wallet
Support for the Oracle Advanced Security (OAS) data encryption and data integrity feature, including support for the following new connection properties:
DataIntegrityLevel sets the level of OAS data integrity used for data sent between the driver and database server.
DataIntegrityTypes specifies one or multiple algorithms to protect against attacks that intercept and modify data being transmitted between the client and server when OAS data integrity is enabled using the DataIntegrityLevel property.
EncryptionLevel determines whether data is encrypted and decrypted when transmitted over the network between the driver and database server using OAS encryption.
EncryptionTypes specifies one or multiple algorithms to use if OAS encryption is enabled using the EncryptionLevel property.