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.  
• Third-party Components Compatibility Matrix: Provides the latest information about the third-party components installed with the product.  

Version 7.1.6

Enhancements

• Some components of the driver are now compiled with a Visual Studio 2022 compiler for Windows platforms. As a result, you must have Microsoft Visual C/C++ runtime version 14.40.33810 or higher on your machine to run the driver.*
• 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.*
• Note: OpenSSL library 3.0.9 has been replaced with a later version. For the latest information about the third-party components that are installed with the product, refer to the Third-party Components Compatibility Matrix.
  The default version of the OpenSSL library has been upgraded to version 3.0.9, which fixes the security vulnerabilities listed on the following page: https://www.openssl.org/news/vulnerabilities-3.0.html.*

  Notes:

  • The driver supports the following OpenSSL 3.0 providers: Default and FIPS.
  • The FIPS provider is supported only on the following platforms: Windows 64-bit, Linux 64-bit, and AIX 64-bit.
  • When installing a new version of the product, the installer program will automatically replace the OpenSSL 1.1.1 library files with the OpenSSL 3.0 library files in the install directory, which will impact all the DataDirect ODBC drivers installed on a machine. Therefore, if you are using multiple 7.1 drivers, upgrade all your drivers to the latest version.

  Refer to TLS/SSL Server Authentication and TLS/SSL Client Authentication 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 Batch Mechanism connection option has been added to the driver. When BatchMechanism is set to 2 (MultiRowInsert), the driver executes a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts. Refer to Batch Mechanism for details.
• The driver has been enhanced to support SSL encryption, which can be configured using the following new connection options: Crypto Protocol Version, CrypoLibName, Encryption Method, Host Name in Certificate, Key Password, Key Store, Key Store Password, SSLLibName, Trust Store, Trust Store Password, Validate Server Certificate. SSL support was formally certified against driver version 07.16.0317 (B0386, U0249). Refer to TLS/SSL Server Authentication and TLS/SSL Client Authentication for details.
  
• The driver has been certified with Apache Sentry for Impala 1.1 and higher. Sentry enables administrators to control access to data and metadata stored on an Hadoop cluster by defining user roles and permissions. Refer to Apache Sentry for details.
  
• The driver has been enhanced to support Kerberos Authentication. Refer to Kerberos Authentication for details.
  
• The driver has been enhanced to support the Char, Decimal, and Varchar data types when connected to Impala 2.0 and higher. Refer to Data Types for details.
  
• The Array Size connection option has been refreshed to allow specifying the number of cells retrieved instead of rows. By determining the fetch size based on the number of cells, the driver can avoid out of memory errors when
  fetching from tables containing a large number of columns. Refer to Array Size 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.
• 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.
• The product no longer includes version 1.1.1 of the OpenSSL library. The library will reach the end of its product life cycle in September 2023 and will not receive any security updates after that. Note that continuing to use the library after September 2023 can potentially expose you to security vulnerabilities.*

  Note: As a result of this change, when installing a new version of the product, the installer program will automatically remove version 1.1.1 of the library from the install directory, which will impact all the DataDirect ODBC drivers installed on a machine.

• The product no longer includes version 1.0.2 of the OpenSSL library. The library has reached the end of its product life cycle and is not receiving security updates anymore. Note that continuing to use the library could potentially expose you to security vulnerabilities.*
  Note: As a result of this change, when installing a new version of the driver, the installer program will automatically remove version 1.0.2 of the library from the install directory.
• The Allowed OpenSSL Versions (AllowedOpenSSLVersions) connection option has been deprecated as the driver currently supports only version 3.0 of the OpenSSL library.
• The crypto protocol versions prior to TLSv1 are no longer supported.
• The AuthenticationMethod connection option has been refreshed with a new valid value for enabling Kerberos Authentication. To use Kerberos  authentication with the driver, set AuthenticationMethod=4. Refer to Authentication Method for details.
  

Notes, Known Issues, and Limitations

• Impala is not designed for OLTP workloads and does not offer real-time queries or row-level updates. Impala is instead designed for batch type jobs over large data sets with high latency.
• Known Issues for Cloudera Impala
  
  • No support for transactions
  • No support for canceling a running query
  • No support for row-level inserts, updates, or deletes
  • No support for cursors or scrollable cursors
  • No support for prepared statements
• The Impala server uses the default port number 21050 unless changed by the system administrator. Use this port number when configuring your driver or consult with your system administrator.
• Do not use port number 21000 that is provided in the Beeswax and Cloudera ODBC driver version 1.2 documentation unless your system administrator has designated this as the port number for your connection. Using this port number will return a connection error.
• The driver does not support specifying values for the same connection option multiple times in a connection string or DSN. If a value is specified using the same attribute multiple times or using both long and short attributes, the connection may fail or the driver may not behave as intended.
• If your database has not been fixed to address the Logjam vulnerability, you can still use the most recent version of the OpenSSL Library by disabling the Diffie-Hellman cipher suites. To disable the Diffie-Hellman cipher suites, specify the following value for the undocumented CipherList connection option:
  CipherList=DEFAULT:-DH
  If you have already specified a value for CipherList, add the following to the existing value:
  :-DH
  The option-value pair for undocumented options can be specified in the odbc.ini, connection string, or the Extended Options field of the GUI. For details, refer to "Configuring and Connecting to Data Sources" in the individual driver chapters of the DATADIRECT CONNECT SERIES FOR ODBC USER'S GUIDE.
• 126 Error When Modifying Data Sources on Windows 10
  You may receive a 126 error when adding or configuring a data source stored on a network location. This is caused by the settings of the User Account Control (UAC) security feature on Windows 10. To work around this issue:
  
  1. From the Start menu, type regedit in the search field; then, select regedit from the results list. The Registry Editor window opens.
  2. Navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. Right click on the subkey; then, select New > DWORD Value.
  4. Rename the new value EnableLinkedConnections.
  5. Right-click EnableLinkedConnections, and then click Modify. The Edit DWORD Value window opens.
  6. In the Value data field, type 1. Click OK.
  7. Close the Registry Editor; then, restart your computer.
  
  Important: Implementing this fix disables security safeguards that are designed to protect your machine. Before starting, refer to the following Microsoft documentation for potential risks associated with disabling the UAC feature: http://windows.microsoft.com/en-us/windows/what-are-user-account-control-settings
• If you have installed an evaluation copy of the drivers and want to upgrade to a licensed version, you must use the Modify option of the installation program.
• When you first install a driver, you are given the option to install a default data source for that driver. We recommend that you install default data sources when you first install the drivers. If you do not install the default data source at this time, you will be unable to install a default data source for this driver later. To install a default data source for a driver after the initial installation, you must uninstall the driver and then reinstall it.
• When trying to connect to a database using SSL encryption, you may receive an error message similar to: "PRNG not seeded". This is because certain versions of some operating systems do not generate truly random numbers necessary for encryption. For more information about this error and available patches, please refer to the Web site: http://www.openssl.org/support/faq.html#USER1
  On SUSE Linux Enterprise Server 10.0, attempts by the drivers to connect using SSL Encryption will not succeed due to a problem loading the SSL libraries.
• The Linux ODBC Administrator does not correctly save the encrypted truststore password, keystore password, and key password in the odbc.ini file when specifying them on the Security tab of the driver Setup dialog boxes. To set these connection options, you must edit the odbc.ini file directly and use the appropriate connection string attributes to store these passwords in the file. You cannot use the driver Setup dialog boxes. See the DATADIRECT CONNECT SERIES FOR ODBC USER'S GUIDE for details about the Security tabs and the odbc.ini file.
• All of the Release 7.1 Core Components (header files, etc.) needed for development of ODBC applications on UNIX and Linux are installed into the /include directory created by the product installer.
  Please read the notices.txt file in the installation directory for licensing information regarding the ODBC Core Components. Contact your Progress DataDirect representative if you have any questions.
  Developers using programming languages other than C++:
  The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC Driver Manager can be used with any language that supports loading a C++ shared library; however, if you are using a programming language other than C++, you must take additional steps to ensure that the C++ libraries are initialized properly when loaded. If you are not using C++, consult your compiler documentation for instructions on using C++ shared libraries with your application.
• A default installation of the product on UNIX and Linux assumes that the value of the LANG environment setting is en_US. If your locale is not set to en_US, the drivers may not return error messages properly. In this case, you must create a symbolic link in the <Install_Dir>/locale directory that has the same value as the LANG environment setting. This link must point to the <Install_Dir>/locale/en_US directory.
• The column attributes 1001 and 1002, which were assigned as DataDirect-specific attributes, were inadvertently used as system attributes by the Microsoft 3.0 ODBC implementation. Applications using those attributes must now use 1901 and 1902, respectively.
• Because of inconsistencies in the ODBC specification, users attempting to use SQL_C_NUMERIC parameters must set the precision and scale values of the corresponding structure and the descriptor fields in the Application Parameter Descriptor.
• For Developers Using IIS: One of the most common connectivity issues encountered while using IIS (Microsoft's Internet Information Server) concerns the use and settings of the account permissions. If you encounter problems using DataDirect drivers with an IIS server, refer to KnowledgeBase document number 4274 on the Progress DataDirect web site: http://knowledgebase.datadirect.com.
• For AIX Users: Some IBM AIX C compilers, such as xlc 3.1.4, do not support the use of C++ build binaries. C developers on AIX should consult their compiler documentation and verify that their AIX C compiler supports the use of C++ shared libraries or the application could be unstable.
  Unexpected behavior may occur randomly if the LIBPATH variable exceeds 178 characters AND the ORACLE_HOME variable is relatively long. To resolve this, create a shorter symbolic link for ORACLE_HOME.

Version 7.1.5

No features introduced 

Version 7.1.4

Enhancements

• The new KeepAlive connection option allows you to use TCP Keep Alive to maintain idle TCP connections.

Version 7.1.3

No features introduced 

Version 7.1.2

Supported with the following Apache Hive versions:

• Cloudera Impala database server and formally certified with the following File formats and storage handlers:
  • File Formats: Parquet, Text File
  • Storage Handlers: HBase

Features

• Returns result set metadata for parameterized statements
  that have been prepared but not yet executed.
• Supports parameter arrays, processing the arrays as a series of
  executions, one execution for each row in the array.
• Provides a connection option that allows you to configure
  the driver to report that it supports transactions, although
  Hive does not support transactions. This provides a workaround
  for applications that do not operate with a driver that reports
  transactions are not supported.
• Provides a connection option that allows you to set a default limit for
  the number of rows returned when an ORDER BY clause is submitted. This
  provides a workaround for applications that are not compatible with
  Impala's requirement that ORDER BY clauses limit the number of rows returned.
•  The driver provides support for the following standard SQL
  functionality:
  • Create Index, Create Table, and Create View
  • Insert, Update, and Delete
  • Drop Index and Drop Table