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 8.0.2

Enhancements

• The driver has been enhanced to support authentication using Microsoft Entra ID (Azure Active Directory) access tokens. You can configure this authentication using the updated Authentication Method (AuthenticationMethod) connection option and the new Entra Access Token (EntraAccessToken) connection option. Refer to Entra ID access token authentication for details.
  Available: 2/25/2025 | 08.02.3777
• The driver is now compiled with a Visual Studio 2022 compiler for the 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.
• The driver has been enhanced to support the TLSv1.3 cryptographic protocol. As part of this enhancement, the default cryptographic protocols enabled by the driver have been updated to TLSv1.3 and TLSv1.2. Refer to the  Crypto Protocol Version for details.*
  Available: 5/20/2024 | 08.02.3308
• 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 AIX platforms:
  • For the 32-bit driver: From libivicu28.a to libivicu.a
  • For the 64-bit driver: From libddicu28.a to libddicu.a
  Notes:
  • This upgrade does not apply to the other UNIX platforms.
  • Available: 5/20/2024 | Build 08.02.1072 of the ICU library files
• 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: From ivicu28.dll to ivicu.dll
  • For the 64-bit driver: From ddicu28.dll to ddicu.dll
  Available: 5/20/2024 | Build 08.02.1072 of the ICU library files
• 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms.
  This upgrade is available starting in build 08.02.0965 of the ICU library files.*
• 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.
  • The following Oracle Advanced Security algorithms are not supported with OpenSSL 3.0:
    • Data Integrity algorithms: MD5 and SHA1
    • Encryption algorithms: RC4_128, RC4_256, RC4_40, and RC4_56
  • 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 8.0 drivers, upgrade all your drivers to the latest version.
    • If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll/libxxtls27.so[.sl] file to a different location before installing a new version of the 8.0 driver. Copy it back to the install directory once the installation is complete.
  • The driver is currently unable to establish a Kerberos connection with Oracle 18c servers.

  Refer to TLS/SSL Server Authentication and TLS/SSL Client Authentication for details.

• The driver has been enhanced to support the Windows certificate store for TLS/SSL server authentication. Refer to the TLS/SSL server authentication for details.*
• The driver has been enhanced to support TLS/SSL server authentication for the applications deployed in a serverless environment. The driver stores the TLS/SSL certificates in memory and lets applications use TLS/SSL server authentication without storing the truststore file on the disk. To use this enhancement, specify the content of the certificate in the refreshed Trust Store (Truststore) connection option or the new SQL_COPT_INMEMORY_TRUSTSTORECERT pre-connection attribute. Refer to the Trust Store and Using SQL_COPT_INMEMORY_TRUSTSTORECERT for details.*
  
• The driver has been enhanced with the new BatchFailureReturnsError option, which determines the behavior of the driver when encountering an error in a parameter array insert with bulk load disabled. Refer to Batch Failure Returns Error for details.*
• 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 driver has been enhanced to support extended connection failover for the connections established using the TNSNAMES.ORA file. Refer to the Configuring failover using the TNSNAMES.ORA file 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 has been enhanced to support Oracle Wallet Password Stores. When this feature is enabled, the driver retrieves database credentials from an Oracle Wallet to be used for authentication to the server. The driver has also been enhanced with the new Credentials Wallet Entry (CredentialsWalletEntry), Credentials Wallet Path (CredentialsWalletPath), Wallet Password (CredentialsWalletPassword) options, which are used to configure this feature. Refer to Oracle Wallet Password Store for details.
• The driver has been enhanced to support connecting using the connection information stored in an LDAP entry. You can configure the driver to use LDAP with the new LDAP Distinguished Name (LDAPDistinguishedName) option and refreshed Host (HostName) and Port Number (PortNumber) options. Refer to Using LDAP for details.
• 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. Refer to Driver Manager and Unicode encoding on UNIX/Linux in Progress DataDirect for ODBC Drivers Reference for details.
  This enhancement is available in build 08.02.0449 of the driver manager.
• The driver has been enhanced to support connecting through Oracle Connection Manager using the TNSNAMES.ORA file. Refer to Oracle Connection Manager for details.*
• The driver has been enhanced to support connecting to a proxy server through an HTTP connection. HTTP proxy support is configurable with the new Proxy Host, Proxy Mode, Proxy Password, Proxy Port, and Proxy User connection options. Refer to Connecting through a proxy server for details.*
  Note: The driver does not currently support SSL data encryption for HTTP proxy connections.
• Support has been added for Oracle Database Vault.*
• The driver has been enhanced with the new Impersonate User connection option that allows you to specify the proxy user ID used for impersonation. The user ID specified using this option determines your permissions and identity when executing queries. Refer to Impersonate User for details.*
• The driver has been enhanced to support using the default Service Name or SID specified in the server-side listener.ora file. Refer to Service Name, SID, and TNSNames File for details.*
• The setting of the Array Size option can now be overridden by specifying the number of rows to fetch using the SQL_ATTR_ROW_ARRAY_SIZE statement attribute. Refer to Array Size for details.*
• Support for Oracle Database Exadata Cloud Service* 
• Support for Oracle Wallet, including:
  • Oracle Wallet SSL Authentication
  • Using Oracle Wallet as a keystore or truststore for SSL data encryption.
  Refer to Oracle Wallet SSL Authentication and Using Oracle Wallet as a keystore for details.
  
• The driver has been certified to use Oracle Internet Directory as a means to store authentication information. Refer to Oracle Internet Directory (OID) for details.
  
• The Oracle driver has been enhanced to support the following new data integrity algorithms for Oracle 12c and higher: SHA256, SHA384, SHA512. To use these algorithms, specify their values using the Data Integrity Types connection option and enable data integrity checks with the Data Integrity Level connection option. Refer to Data Integrity Types and Data Integrity Level for details.
  
• 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.

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 valid value for the Authentication Method (AuthenticationMethod) option for retrieving credential information from Oracle Wallet password stores has been changed from 14 to 16. To support existing configurations of the driver, the original value, 14, will continue to be supported for this version of the driver. See for Authentication Method for details.
• 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 default value for the Data Integrity Types connection option has changed to the following: MD5,SHA1,SHA256,SHA384,SHA512. Refer to Data Integrity Types for details.
  

Notes, Known Issues, and Limitations

• In testing, build 3072 of the driver has been observed to crash intermittently on Solaris platforms. The incident rate is very low and specific to our testing environment, but we are continuing to investigate the root cause of the crash.
• The Trust Store field on the Driver setup dialog supports content up to 8192 characters in length. For specifying certificate content longer than 8192 characters, edit the registry and manually add the entry to the DSN.
• 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.
• The driver uses the XA protocol support in Oracle 8 to provide distributed transaction support. For recovery to work correctly, you must grant appropriate privileges on any server that will participate in a distributed transaction. You must grant the SELECT privilege on SYS.DBA_PENDING_TRANSACTIONS to all users that will use MTS. Refer to the Oracle 8 documentation for details on using Oracle XA.
• 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
• 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
• All of the Release 8.0 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.
• 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.
• 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.
• 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 for details.
• For Microsoft Access Users: Some SQL implementations, such as PROGRESS, do not allow queries to contain the COUNT function without the DISTINCT set quantifier. For example, "SELECT COUNT(empid) FROM employees" is not a valid SQL query for PROGRESS. This type of query can be generated using Microsoft Access and results in an error.
• If you are using Oracle 8.1.7, you must have the 8.1.7.1 server patch installed. Otherwise, you may receive the Oracle error:"ORA-03120: two-task conversion routine: integer overflow" when fetching LOB data.
  SQLProcedures and SQLProcedureColumns now include functions/procedures from Oracle packages. They are denoted in the result set as PackageName.ProcedureName for the PROCEDURE_NAME.
  To use static scrollable cursors with result sets containing long columns, you must set EnableStaticCursorsForLongData (ESCLD) to 1 (EnableStaticCursorsForLongData=1) in the data source entry of the Registry or in a connection string. The default setting is 0.
  You must have a complete installation of the Oracle 8i client software for the Oracle (client) driver to operate properly when accessing remote Oracle 8i servers 8.0.5 or higher. Be sure that you have installed Oracle 8i Client 8.1.7, installation type: Programmer.
  NOTES: On Linux, you must use the Oracle Net8 Client version 8.1.6.1.
• The driver for HP-UX 11 aCC is supported on HP-UX 11.0 when running with HP-UX applications built using the HP aCC compiler version 3.05 or higher.
  The ODBC drivers require certain runtime library patches. HP-UX patches are publicly available from the HP Web site (www.hp.com). The required patch is: PHSS_14577
  HP updates the patch database regularly; therefore, the patch numbers in this file may be superseded by newer versions. If you search for any of the specified patches on an HP site and receive a message that a patch has been superseded, download and install the replacement patch.
  Progress DataDirect provides a shared library creation script named genclntsh816, described in the user's guide. This script is relevant for HP-UX 11 PA-RISC only, not for IPF.

Version 8.0.1

Enhancements

• The driver has been updated with OpenSSL library version 1.0.2k.*
  Note: OpenSSL library 1.0.2k has been replaced with version 1.0.2n.
• Support for the Oracle 12 and 12a authentication protocols, which provide improved security.
• Support for returning implicit result sets from stored procedures.
• The driver is now compiled using Visual Studio 2015 for improved security.
• The new SDU Size connection option allows you to specify the size in bytes of the Session Data Unit (SDU) that the driver requests when connecting to the server.
• The new Support Binary XML connection option enables the driver to support XMLType with binary storage on servers running Oracle 12c and higher. 
• The new LOB Prefetch Size connection option allows you to specify the size of prefetch data the driver returns for BLOBs and CLOBs for Oracle database versions 12.1.0.1 and higher. 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.

Changed Behavior 

• The Enable N-CHAR Support connection option has been deprecated, and the driver behavior has been updated to always provide support for the N-types NCHAR, NVARCHAR2 and NCLOB. For compatibility purposes, the EnableNcharSupport attribute can still be manually specified for this release, but will be deprecated in subsequent versions of the product. 
• The Enable Timestamp with Timezone connection option has been deprecated, and the driver behavior has been updated to always expose timestamps with timezones to the application. For compatibility purposes, the EnableTimestampwithTimezone attribute can still be manually specified for this release, but it will be deprecated in subsequent versions of the product.
• The default value for the Data Integrity Level connection option has been updated to 1 (Accepted). By default, a data integrity check can now be made on data sent between the driver and the database server, if the server request or requires it. This change allows the driver to connect to servers requiring Oracle Advanced Security data integrity checks using the default configuration.
• The default value for the Encryption Level connection option has been updated to 1 (Accepted). By default, encryption is now used on data sent between the driver and the database server if the database server requests or requires it. This change allows the driver to connect to servers requiring Oracle Advanced Security encryption using the default configuration.  

Version 7.1.6

Enhancements

• The default OpenSSL library version has been updated to 1.0.2j.*
  Note: OpenSSL library 1.0.2j has been replaced with version 1.0.2n.
• The default OpenSSL library version has been updated to 1.0.2h.*
  Note: OpenSSL library 1.0.2h has been replaced with version 1.0.2n.
• The default OpenSSL library version has been updated to 1.0.2g.*
  Note: OpenSSL library 1.0.2g has been replaced with version 1.0.2n.
• The default OpenSSL library version has been updated to 1.0.2f.
  Note: OpenSSL library 1.0.2f has been replaced with version 1.0.2n.
• The new CryptoLibName and SSLLibName connection options allow you to 
   designate the OpenSSL libraries used when SSL is enabled.

Version 7.1.5

Enhancements

• The OpenSSL library was upgraded to version 1.0.0r, which fixes the
  CVE‐2015‐0204 (FREAK) vulnerability. See "RSA silently downgrades
  to EXPORT_RSA [Client] (CVE‐2015‐0204)" at
  https://www.openssl.org/news/secadv_20150108.txt for more
  information.
• The new PRNGSeedSource connection option allows you to specifies whether the
  driver uses a file or the RAND_poll function as the seed source for SSL key generation.
• The new PRNGSeedFile connection option allows you to specify the entropy‐source file or device used as a seed for SSL key generation.
• The new Crypto Protocol Version connection option allows you to specify the cryptographic protocols used when SSL is enabled. This option can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.

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

Enhancements

• Modified to support all Oracle 11gR2 Kerberos encryption algorithms.

Version 7.1.2

No features introduced 

Version 7.1.1

No features introduced

Version 7.1.0

Enhancements

• Support for Oracle Advanced Security (OAS).