Fixed issues in DataDirect ODBC 8.0

Connection failed with error 'The value for connection option SQLEngineMode was stored as a ENUM but is being retrieved as a MAP.'

When establishing multiple parallel connections on Linux systems with low kernel entropy, the driver intermittently returned a socket closed error or failed to connect. This was caused by a driver component blocking while waiting for sufficient system entropy.

Intermittent crash in the driver caused by memory corruption during stored procedure execution.

When the {{KeepConnectionActive}} connection option was enabled, the driver encountered a performance regression where {{SQLDisconnect}} calls experienced an unnecessary two-second delay. This issue was resolved by removing a redundant internal wait period that was previously triggered during the disconnect process.

When multiple connections were invoked in parallel on Linux systems, the driver intermittently returned “socket closed” errors during NTLMv2 authentication.

When attempting to connect to a SQL Server named instance with the {{MultiSubnetFailover}} connection option enabled, the driver returned a "Timeout expired" error.

When the MultiSubnetFailover connection option was enabled, the driver intermittently returned a network error if any node in the cluster was unreachable. The driver now correctly continues attempting connections to other available nodes in the cluster until a successful connection is established.

When calling Oracle stored procedures that return CLOB data through input-output parameters, the driver incorrectly returned empty results.

When performing bulk loads to Oracle, the driver encountered data loss in subsequent batches if a row-level error occurred in the initial batch.

When performing bulk loads to Oracle, the driver encountered data loss in subsequent batches if a row-level error occurred in the initial batch.

When attempting to connect using OAuth2 authentication, the driver failed if a user ID was specified in the connection options.

The driver failed with “Number contains an invalid character” error or hung during connection initialization when connecting to EnterpriseDB Advanced Server 15.17 and higher with BDR extension due to incorrect processing of the {{bdr.last_committed_lsn}} parameter.

When an application was compiled with the {{-DSQLWCHARSHORT}} flag on Linux, the driver returned an “invalid byte sequence for encoding UTF8” error when inserting data into text array columns.

When attempting to connect to an Informix 15 database, the driver returned a connection error due to an issue parsing the server version string.

The driver returned an error when calling {{SQLProcedureColumns}} with {{CatalogName}} set to {{NULL}} instead of returning the expected parameter metadata.

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.

Crash occurs at connection time for the latest MySQL, Oracle and PostgreSQL drivers on AIX

Crash occurs at connection time for the latest MySQL, Oracle and PostgreSQL drivers on AIX

Crash occurs at connection time for the latest MySQL, Oracle and PostgreSQL drivers on AIX

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 the SQL Engine Mode was set to Direct and the JVM Classpath connection option was empty, the driver failed to initialize the JVM. This occurred because the driver incorrectly included double quotes in the automatically generated classpath.

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.

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

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.

Updating an existing SharePoint DSN after upgrading the driver erased the Access and Refresh tokens.

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.

Connecting to Amazon Redshift using JWT authentication ({{AuthMethod=39}}) failed in Kubernetes pod environments with an error indicating a missing device or address during file I/O operations.

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 newer SQL Server WP ODBC driver seems to no longer accept a domain name as part of the UID when connecting with AuthenticationMethod=10. If the customer tries to connect, it returns the error:Socket closed :01006 : Login failed.The login is from an untrusted domain and cannot be used with Integrated authentication.

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.

The connection became unusable after a query timeout occurred.

When executing SQLNumResultCols() for an application that limited the number of rows it could receive from the server using the SQL_ATTR_MAX_ROWS attribute, the driver returned an incorrect result.

When attempting to reuse a connection from a pool containing 100 bad connections, the driver took more than 15 minutes to time out the connection.

The HostName and ServerName connection options must be exposed for the ODBC and JDBC drivers, respectively.

When attempting to execute a SELECT query containing the DISTINCT keyword, the returned an incorrect result set.

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.

When attempting to run SQLDescribeCol() and SQLColumns() functions for a column of Vector data type, the driver returned an incorrect precision.

The driver failed to provide failover support for connections to the LDAP server.

An automatic crash reporting system showed that the driver stopped responding during a fetch operation.

On Windows, when attempting to establish a connection using a DSN that does not contain the user name, the driver returned the following error: “Insufficient information to connect to the data source”.

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 attempting to create the driver package, the Bind tool returned the following error: “Specified driver could not be loaded.“

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 the LD_LIBRARY_PATH environment variable is set on the Linux z/OS platform, the branded driver is not using the correct ICU file.

When sampling or querying data in lines of XML that contained attributes and plain text, the driver processed the attribute information but ignored the plain text data.

Chinese characters like “瞇眼” failed to insert into the database using the UTF-8 encoding.

The metadata returned by the ODBC driver for Azure Synapse does not match the metadata returned by the JDBC driver.

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.

A Windows compiler flag, Control Flow Guard (CFG), was not enabled for the driver.

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.”

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

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.

The driver has been updated to remove all values that should be secured from generated log files.

The driver has been updated to remove all values that should be secured from generated log files.

When attempting to insert 605 characters into an NCLOB column using InterpretWCharColumnSizeAsByteCount=1, the driver inserted only the first 303 characters.

The ODBC.ini file installed as part of the alldrivers package for Linux does not contain the DSN configuration details for the Google Analytics 4 driver.

The ODBC GoogleBigQuery driver does not honor the “UseStreamingInsert” connection option after Re-running the same job, causing a huge performance issue.

A crash occurred when the application attempted to retrieve diagnostic records for SQLCancel while canceling a function on another thread.

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

In certain scenarios, the driver accessed invalid memory when calling SQLSetConnectAttribute, which led to an access violation.

When BULK MODE was enabled, the driver failed to insert the Varchar2 (n CHAR) data that exceeded the precision.

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.”

When attempting to authenticate using a password longer than 35 characters, the driver returned an error.

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.

When attempting to execute SQLGetInfo(SQL_DBMS_VER), the driver returned an incorrect database version.

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

When attempting to fetch metadata without specifying the database name, the driver took a long time to return the metadata.

The driver has been enhanced to support connecting to Snowflake partner applications. Use the new Partner Application Name connection option to specify the name of the partner application to which you want to connect.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

.When the driver calls SQLGetDiagRecW function, ODBC Trace is incorrectly adding a leading space to certain entries in the log.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

The driver failed to log XA calls when ODBC trace was enabled.

When attempting to fetch rows larger than 2GB, the driver returned the following error: “fetch row count exceeds MINSWORDMAXVAL.”

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 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.

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

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

The driver has been updated to resolve a potential security vulnerability detected in a BinSkim scan.

When Kerberos Authentication was enabled, build 08.02.2584 of the driver failed to connect to an Oracle database server that had the July 2021 (or more recent) Critical Security Patch applied.

SQL Injection in ODBC Driver

Buffer Overflow - Function Called With Small Buffers

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.