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.
Version 5.1.4
CERTIFICATIONS
Certified with DB2 V11.5 for Linux, UNIX, Windows* Driver version 5.1.4.000288 (F000439.U000210)
Certified with Oracle JDK 11* Driver version 5.1.4.000237 (F000378.U000183)
Certified with OpenJDK 11* Driver version 5.1.4.000237 (F000378.U000183)
Certified with OpenJDK 8 on Windows and Linux* Driver version 5.1.4.000237 (F000378.U000183)
Certified with IBM Db2 Hosted* Driver version 5.1.4.000207 (F000348.U000165)
Certified with DB2 V12 for z/OS* Driver version 5.1.4.000217 (F000355.U000174)
Certified with dashDB (Db2 Warehouse on Cloud)* Driver version 5.1.4.000207 (F000348.U000165)
Certified with DB2 V11.1 for Linux, UNIX, Windows*
Certified with DB2 for i 7.3* Driver version 5.1.4.000187 (F000323.U000141)
Certified with DB2 for i 7.2
ENHANCEMENTS
The driver has been enhanced to support the Generic Security Standard (GSS) plug-in for authentication. The plug-in consists of a set of APIs that you can implement to customize your authentication requirements and interoperate with various security methods. You can configure a GSS plug-in using the refreshed AuthenticationMethod property and the new GSSPluginName and GSSPluginObject properties.*
The driver has been enhanced to support connecting to a proxy server through an HTTP connection. HTTP proxy support is configurable with the new ProxyHost, ProxyMode, ProxyPassword, ProxyPort, and ProxyUser connection properties.*
The KeepAlive connection property has been added to the driver. Enabling the KeepAlive property allows the client to keep idle TCP connections active by periodically passing packets to the server.*
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.*
Support for cursor type OUT parameters for DB2 for Linux, UNIX, Windows stored procedures has been added to the driver.*
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.
Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
Java SE 7 has reached the end of its product life cycle and will no longer receive generally available security updates. As a result, the drivers will no longer support JVMs that are version Java SE 7 or earlier. Support for distributed versions of
Java SE 7 and earlier will also end, including IBM SDK (Java Edition).*
For DB2 for z/OS, the AlternateID connection property has been modified to set the name of the schema in the DB2 CURRENT SCHEMA special register instead of the DB2 CURRENT SQLID special register. AlternateID now sets the name of the schema in the
CURRENT SCHEMA special register for DB2 for i, DB2 for Linux/UNIX/Windows, and DB2 for z/OS.*
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.*