An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  

Version 7.1.6

Enhancements

• For AIX platforms, the ICU library files that are installed with the product have been upgraded to version 74.1. As a part of this upgrade, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from libivicu28.a to libivicu.a. For the 64-bit driver, the ICU file name has changed from libddicu28.a to libddicu.a. Notes:
  • This upgrade does not apply to the other UNIX platforms.
  • This upgrade is available starting in build 08.02.1072 of the ICU library files.
  • libivicu27.a (32-bit) and libddicu27.a (64-bit) will continue to be included in the product package to support driver functionality.
• For Windows platforms, the ICU library files that are installed with the product have been upgraded to version 74.1. As a part of this upgrade, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from ivicu28.dll to ivicu.dll. For the 64-bit driver, the file name has changed from ddicu28.dll to ddicu.dll. Notes:
  • This upgrade is available starting in build 08.02.1072 of the ICU library files.
  • ivicu27.dll and ddicu27.dll will continue to be included in the product package to support driver functionality.
• The Driver Manager has been upgraded to version 8.0. The purpose of this upgrade is to have all DataDirect for ODBC drivers use the latest version of the Driver Manager, which allows for faster security updates and a consistent user experience. Note that the Driver Manager is backward compatible. As part of this upgrade:
  • The following ICU library files have been added to the product package:
    • For UNIX: libivicu28.so (32-bit) and libddicu28.so (64-bit)
    • For Linux: libivicu.so (32-bit) and libddicu.so (64-bit)
  • The trace library file names have been changed for both UNIX and Linux:
    • 32-bit: From ivtrc27.so to ivtrc28.so
    • 64-bit: From ddtrc27.so to ddtrc28.so
  Note 1: libivicu27.so (32-bit) and libddicu27.so (64-bit) will continue to be included in the product package to support driver functionality.
  Note 2: The Driver Manager build included with the product is 08.02.1997 (U1987).
• For Linux platforms only, the ICU library files that are installed with the product have been upgraded to version 74.1. In addition, the ICU library file names have changed for Linux platforms:
  • For the 32-bit driver: From libivicu27.so to libivicu.so
  • For the 64-bit driver: From libddicu27.so to libddicu.so
  This upgrade is available starting in build 08.02.0965 of the ICU library files.
• For Windows platforms, the trace library file names have been changed from ivtrc27.dll to ivtrc28.dll (32-bit) and from ddtrc27.dll to ddtrc28.dll (64-bit) to have the same file names across all platforms. This change allows for faster release of security updates and a more consistent user experience.
  Note: To support the trace library file name change, the following ICU library files have been added to the product package: ivicu28.dll (32-bit) and ddicu28.dll (64-bit).
• A Password Encryption Tool, called ddencpwd, is now included with the product package. It encrypts passwords for secure handling in connection strings and odbc.ini files. At connection, the driver decrypts these passwords and passes them to the data source as required. See Password Encryption Tool (UNIX/Linux only) for details.*
• The drivers using base version B0649 and later have been enhanced to include timestamp in the internal packet logs by default. If you want to disable the timestamp logging in packet logs, set PacketLoggingOptions=1. The internal packet logging is not enabled by default. To enable it, set EnablePacketLogging=1.*
• The Driver Manager for UNIX/Linux has been enhanced to support setting the Unicode encoding type for applications on a per connection basis. By passing a value for the SQL_ATTR_APP_UNICODE_TYPE attribute using SQLSetConnectAttr, your application can specify the encoding at connection. This allows your application to pass both UTF-8 and UTF-16 encoded strings with a single environment handle.
  The valid values for the SQL_ATTR_APP_UNICODE_TYPE attribute are SQL_DD_CP_UTF8 and SQL_DD_CP_UTF16. The default value is SQL_DD_CP_UTF8.
  This enhancement is available in build 07.16.0398 of the driver manager.
• The new NamedIDBehavior config option allows you to determine whether the Name attribute of NamedID fields is exposed in the relational map. This option can be used to avoid "poor performing query" errors by reducing the size of result sets. Refer to "Poor performing query" error message and NamedIDBehavior (Config Option) for details.*
• The new Min Long Varchar Size connection option allows you to fetch SQL_LONGVARCHAR columns whose size is smaller than the minimum imposed by some third-party applications. Refer to Min Long Varchar Size for details.
• The new Varchar Threshold connection option allows you to fetch columns that would otherwise exceed the upper limit of the SQL_VARCHAR type for some third-party applications. Refer to Varchar Threshold for details.

Changed Behavior

• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.

  Notes:

  • This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  • The installer program cannot remove the already installed JRE files from the install directory automatically. Remove them manually.
  • To install the 32-bit drivers on 64-bit Windows platforms and start the SQL engine service, the installer requires the 32-bit version of Java SE 11 or higher installed on your machine and defined on your path.
• The product package no longer includes the ODBC Cursor library file (odbccurs.so) because it has some known security vulnerabilities that could potentially expose you to security risks.*
  Note: The installer program cannot remove the ODBC Cursor library file automatically while installing a new version of the driver. Remove it manually.

Version 7.1.5

Features

• The driver supports Oracle RightNow CX API
• Supports all ODBC Core functions. 
• Supports the core SQL-92 grammar.
• Supports client-side data caching.