Fixed issues in DataDirect ODBC 8.0

OAuth token retrieval and connection testing failed in the ODBC configuration workflow when using newer Java runtimes.

OAuth token retrieval and connection testing failed in the ODBC configuration workflow when using newer Java runtimes.

OAuth token retrieval and connection testing failed in the ODBC configuration workflow when using newer Java runtimes.

OAuth token retrieval and connection testing failed in the ODBC configuration workflow when using newer Java runtimes.

Request to provide the Pre-QA build with OpenSSL changes.

When attempting to copy data into Microsoft Fabric Data Warehouse, the driver failed and returned “SSL I/O Error” and “Socket Closed” errors.

When attempting to connect to Microsoft SQL Server Fabric, the driver returned the following error:”Unable to dynamically load client library [libS0curl28.so|http://libS0curl28.so]: CURL initialization failure.”

The driver returned an error on the SQLTablesW call when connected to a PostgreSQL 18.0 database.

The driver returned an error because curl continued to search for the default libssl.so and libcrypto.so libraries, despite custom SSL and crypto library names being configured.

The driver could not fetch table metadata when the table name contained special characters.

When attempting to establish a connection in proxy mode, the driver failed to resolve libcrypto.dll correctly and returned the following error: “The procedure entry point EVP_get_id could not be located in the dynamic link library”

The user observed unusually high RAM usage when SSL was enabled for SQL Server connections on Linux PPC‑LE, indicating a potential memory leak.

A PLS‑00306 error occurred when calling the stored procedure AP_ACCT_DISCOVER after Oracle Patch is introduced with an Object ID larger than 2147483647.

Some column names differed from the expected schema (e.g., {{_SLAINVOKEDID_VALUE}} vs. {{SLAINVOKEDID}}), and certain lookup fields lacked corresponding YOMI name attributes.

OAuth token retrieval and connection testing failed in the ODBC configuration workflow when using newer Java runtimes.

OAuth token retrieval and connection testing failed in the ODBC configuration workflow when using newer Java runtimes.

The user could not use a third-party driver because the license file did not include the branded Driver Manager.

When connecting to Db2 with the Authentication Method set to 1 (Encrypted Password with DES), the driver failed with the incorrect AES security mechanism error, "Specified security mechanism Encrypt Password (AES) is not supported by the server," instead of falling back to DES.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The OpenSSL library component of the driver has been upgraded to version 3.0.19 to resolve the CVE-2025-15467 security vulnerability.

The driver returned an error where batch inserts with non-UTF8 character sets resulted in an invalid encoding failure.

The driver continued issuing FETCH requests after a numeric overflow error, causing the application to hang instead of terminating the query.

The driver returned an incorrect data type for quoted Char columns, reporting them as Tinyint instead of a character type.

The driver returned an incorrect SQLState for a dead connection, reporting HY000 instead of the 08S01 communication‑link‑failure code.

The driver encountered network failures with SSL‑enabled connections when processing large data volumes against SQL Azure, resulting in intermittent 08S01 errors.

The driver returned inconsistent data types for TIMESTAMP WITH TIME ZONE columns, reporting TIMESTAMP via SQLColumns but CHAR via SQLDescribeCol.

Insert statements using SQLParamData/SQLPutData were corrupted by the Hive ODBC driver, which replaced the parameter marker and opening parenthesis with ,1 and caused invalid SQL syntax.

On Linux, the driver failed to connect to an instance of Azure Databricks Warehouse using token-based authentication.

When Oracle wallet contained more than five entries, the connection failed.

Insert operation for the minimum {{SMALLMONEY}} value ({{-214748.3648}}) failed when column encryption was enabled, due to incorrect handling of 32-bit integer negation during parameter binding in prepared statements.

When connecting using OAuth with a token that exceeded 2558 characters, the data source was not saved and the driver returned the error “Updating Configuration Failed.”

SQLExecute() hanged indefinitely when executing PostgreSQL stored functions with return values.

Insert queries failed when using the {{SQL_variant}} data type with column encryption.

When using the SQLProcedureColumns() API with the driver, the driver incorrectly returned DECIMAL_DIGITS = 0 for a parameter defined as TIMESTAMP or TIME.

When attempting to use TLS/SSL encryption, the driver encountered memory leak issues.

When executing SQLPrepareW, the driver intermittently crashed and impacted the customer’s production system.

The driver failed to load data from the {{EMAILS}} table when executing a {{SELECT}} query against the data source.

When executing a getSchemas() call, the driver did not return schemas whose names were enclosed in double quotes.

When filtering endpoints that require parameters using {{INFORMATION_SCHEMA.SYSTEM_COLUMNS_REQUIRED_FILTERS}}, the required filter was not exposed in the path for the {{PROPERTIESLIST}} endpoint.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

The native Informix driver returned inconsistent results when reading chunked CLOB data through the DataDirect Driver Manager.

When fetching data from a large table with FailoverMode set to 2(Select) and using SQLCloseCursor(), the driver stopped responding.

When attempting to use TLS/SSL encryption, the driver encountered memory leak issues.

Re-executing a prepared stored procedure after a {{QueryTimeout}} caused syntax and sequence errors, indicating that the statement was invalidated.

The driver returned an ORA-00910 error when executing a query to check for Extended Data Types (EDT) support in environments where EDT was not enabled.

The Configuration Manager incorrectly added extra backslashes to file paths after clicking the “Update” button.

Repeated execution of a stored procedure without re-preparing the statement caused decimal values to lose trailing zeros in the output.

The driver returns table names only in plural form. It should support returning names in both singular and plural forms.

The Google BigQuery ODBC driver incorrectly indicated support for stored procedures.

On Linux, the Progress driver manager crashed when attempting to connect to the native Db2 driver.

When fetching data with UTF8 encoding from Microsoft Fabrics Data Warehouse, the data was truncated.

The driver failed to connect to Azure Databricks 4.0.0 over HTTP transport and returned a 400 status error.

The driver returned an "Invalid character value" error when executing a stored procedure. However, it successfully executed a similar stored procedure with different parameters.

When initiating an XA connection to the database, the driver failed during the xa_recover call with an XAER_RMERR (-3) error.

When attempting to run a stored procedure, the driver returned the result set in an incorrect order.

The latest version of the driver did not perform as well as its earlier version.

When attempting to execute a stored procedure, the application crashed.

When using the SQLExecDirect function to perform a bulk insert of 3000 rows, the server returned an HTTP 400 Bad Request error and the SQL operation stalled.

When attempting to execute SQLDescribeCol, the driver incorrectly mapped the BIT data type to SQL_VARCHAR instead of the expected SQL_BIT (-7) during metadata retrieval and query execution.

Applications compiled with the Solaris {{cc}} compiler may be unable to load the Google BigQuery driver.

When attempting to perform a batch insert using BatchMechanism=2, the driver inserted null values instead of timestamps.

When using Entra ID (Azure AD) authentication, the connection failed with a “Socket Closed” error.

The following error occurred when attempting to execute a stored procedure with more than 32 parameters: “Wrong number of parameters: 35 requested but 32 returned.”

The driver failed during the SQLDriverConnectW() call in FIPS Mode with a Non-SSL configuration.

A fatal error occurred when the driver attempted to execute a PL/SQL command through an IBM Datastage job.

A driver regression occurred that resulted in SQLDescribeParam failing when the driver executed an UPDATE statement through DBLINK.

When ServerMode=1 (Server), the driver hung when attempting to connect using SQLDriverConnectW.

When attempting to use custom OpenSSL libraries, which were specified using the SSLLibName and CryptoLibName options, the driver returned the following error: “Unable to determine the OpenSSL version for libssl-3-x64.dll”.

When attempting to use the custom OpenSSL libraries, specified using the SSLLibName and CryptoLibName connection options, the driver returned the following error: “Unable to determine the OpenSSL version for libssl-3-x64.dll.”

When attempting to use custom OpenSSL libraries, which were specified using the SSLLibName and CryptoLibName options, the driver returned the following error: "Unable to determine the OpenSSL version for libssl-3-x64.dll."

On Windows platforms, the driver failed to connect with the following error when attempting to use custom SSL libraries: “Unable to determine the OpenSSL version .dll.”

On Windows platforms, the driver failed to connect with the following error when attempting to use custom SSL libraries: “Unable to determine the OpenSSL version .dll.”

On Windows platforms, the driver failed to connect with the following error when attempting to use custom SSL libraries: “Unable to determine the OpenSSL version library_name.dll.”

On Windows platforms, the driver failed to connect with the following error when attempting to use custom SSL libraries: “Unable to determine the OpenSSL version .dll.”

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The default OpenSSL library has been upgraded to version 3.0.15 to fix potential security vulnerabilities.

The driver returned incorrect parameter descriptions when attempting to run a query containing two untyped parameters.

The driver failed to connect to SharePoint using OAuth2.0 authentication via Oracle Gateway.

When attempting to execute SQLBindParameter() with a column size that is greater than the column size of the database, the old driver returned SQL_SUCCESS_WITH_INFO (error message: String data, right truncated) and the new driver returned SQL_ERROR (error message: value too large for column).

The CLOB data got corrupted when getting inserted into the target table.

The latest version of the driver failed to connect to the server using Entra ID (Azure Active Directory) authentication using user ID and password (AuthenticationMethod=13).

The driver was unable to use the Google BigQuery Streaming API when executing INSERT statements containing table, dataset, or project names that included a backtick (`) character.

When attempting to connect using the driver build 3072 or higher, the OS_USER was recorded as an "UNKNOWN_USER" resulting in an application error.

If StrLen_or_IndPtr of SQLBindParameter was set to 0, the driver failed to return data in the result for a function/stored procedure call.

The driver threw an exception when attempting to execute a query to fetch a report (stored procedure).

Calling SQLDescribeParam() failed when a statement contained a table alias and parameters.

The driver returned a general, non-informational error message when attempting to authenticate using the Service Account authentication by specifying an empty .json file for the Service Account Private Key connection option.

The driver failed to connect to the Azure server when attempting to use a redirect policy.

When the Cached Description Limit connection option was set to a value greater than zero, the 08.02.2621 version of the driver crashed when attempting to run the same query multiple times.

"When the hidden connection option KeepConnectionActive=1, the driver would intermittently hang when trying to execute certain jobs."

The driver failed to call the stored procedure that uses an OUT parameter in its signature.

The driver failed to call the stored procedure that uses an OUT parameter in its signature.

Incorrect default value documented for XMLDescribeType (SQL_WLONGVARCHAR) in the DB2 ODBC User Guide.

The installer program failed to install the ddencpwd tool, ddtestlib tool, and samples on the Little Endian Linux for Power8 platform.

The installer program failed to install the ddencpwd tool, ddtestlib tool, and samples on the Little Endian Linux for Power8 platform.

The driver returned incorrect results when executing the SQLFetch method.