16 TERADATA
============================================================================== Simba Teradata ODBC Data Connector Release Notes ==============================================================================
The release notes provide details of enhancements, features, known issues, and workflow changes in Simba Teradata ODBC Connector 20.00.00.048, as well as the version history.
This version of the connector supports the following data source versions and platforms (Note: Platforms included with a distribution may vary according to what has been licensed): * Teradata Vantage (20.00), Vantage Cloud (20.00), 17.20 Database, 17.10 Database, 17.00 Database * Windows 11, Windows 10, Windows Server 2025, 2022, 2019, 2016 * macOS 13, 14, 15 * Linux (x86_64 and ARM64): RHEL 8/9, SLES 15, Debian 11/12, Ubuntu 22.04/24.04, SUSE Linux Enterprise Server 15
20.00.00.048 =================================================================
Released 2026-03-25
Enhancements & New Features
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.048.
Known Issues The following are known issues that you may encounter due to limitations in the data source, the connector, or an application.
[SENTDO-73] Statement info parcel returns errors for TIME parameters.
When using statement info parcel and stored procedures with a TIME parameter are called, the connector returns an error.
Some custom fields are not supported for SQLGetDescField.
When calling SQLGetDescField, the connector does not support the SQL_DESC_TD_ACTIVITY_TYPE and SQL_DESC_TD_COST_ESTIMATE custom header description fields.
Catalog functions always return ODBC 3.x column names.
For catalog functions, the connector returns the ODBC 3.x column names rather than ODBC 2.x column names, even in an ODBC 2.x environment.
The setting for the SQL_ATTR_ROWS_FETCHED_PTR statement attribute does not persist.
You can set a value by calling SQLSetStmtAttr(SQL_ATTR_ROWS_FETCHED_PTR), but the value is reset after you close the cursor.
In specific cases, during INSERT operations that require the data to be truncated, there is no message indicating that truncation has occurred.
This behavior occurs when both of the following conditions are met:
- The Session Mode option (the SessionMode property) is set to Teradata.
- The connector inserts data that is too large for the target column.
The database truncates the data to fit, but the message indicating that truncation has occurred is not returned. The connector expects the database to report the truncation. However, when Session Mode is set to Teradata, the database does not return the truncation message.
Workflow Changes =============================================================
The following changes may disrupt established workflows for the connector.
20.00.00.003 —————————————————————–
[SENTDO-2717] Updated default login timeout
The new default login timeout is 60 seconds. Previously, it was 20 seconds.
Version History ============================================================== 20.00.00.047 —————————————————————–
Released 2026-03-09
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.047.
[SENTDO-3158] Fixed regression issue where columns following a LOB (BLOB or CLOB) column are corrupted.
[SENTDO-3169] Connection string OIDC_CLIENTID does not take precedence over database configuration’s ClientId in TdgssUserConfigFile.xml.
20.00.00.044 —————————————————————–
Released 2026-02-25
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.044.
[SENTDO-3149][CS3238088] Users are now able to retrieve username using TDWallet.
[SENTDO-3118][SENTDO-3147][CS2871415][CS3326473] Fixed a proxy bypass handling issue so that bypass rules are evaluated against the original destination hostname when reverse DNS is unavailable.
[SENTDO-3124][CS3283207] When retrieving a mix of latin and unicode columns one character is missing from latin columns.
[SENTDO-3127][CS2994349]
- Retrieved data does not convert correctly when “Enable Extended Statement Information” is off.
- Removed call to C API getnameinfo() to do reverse name lookup because this call can be inefficient.
[SENTDO-3128] Log on fails when logintimeout is set to zero.
[SENTDO-3130][CS3248626] Database generates “Datetime field overflow” error when executing SQLExecDirect call on TIMESTAMP(0) column with timestamp data containing fractional seconds (e.g., 13:14:15.000000).
[SENTDO-3153][CS3363124] Fixed an issue where setting any proxy configuration in the DSN connection string caused all proxy environment variables to be ignored; each proxy setting is now resolved independently, with DSN taking precedence over environment variables for the same key.
20.00.00.039 —————————————————————–
Released 2025-12-11
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.039.
[SENTDO-3124][CS3283207] When retrieving a mix of latin and unicode columns one character is missing from latin columns.
[SENTDO-3127][CS2994349] Retrieved data does not convert correctly when “Enable Extended Statement Information” is off.
20.00.00.038 —————————————————————–
Released 2025-12-03
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.038.
[SENTDO-3103] Global Identity Framework Token Refresh Settings Feature
OIDC_REFRESH
OIDC_REFRESH=True (the default) specifies that the connector should use an available refresh token to obtain a new token when the current token expires.
OIDC_REFRESH=False specifies that the connector should ignore an available refresh token.
OIDC_REFRESH_PERCENT
Specifies the OpenID Connect (OIDC) token minimum remaining lifetime percentage for the connector to reuse a token. The connector will replace a token when its remaining lifetime falls below this percentage.
The default percentage of 15 specifies that the connector should reuse a token for the first 85% of its lifetime, and replace it when its remaining lifetime falls below 15%.
Specify 0 to turn off preemptive replacement and use the entire token lifetime. Specify 100 to never reuse a token and always obtain a new token.
[SENTDO-3084] Additional fix: SQLColAttribute(…, SQL_COLUMN_CHARACTER_SET, …) does not return correct charset code.
[SENTDO-3085][CS2871415] When using a proxy server, the connector did not properly track successful socket connections, resulting in repeated connection attempts. This issue was introduced in version 20.00.00.026 and fixed in version 20.00.00.038.
[SENTDO-3113][CS3163518] ClientTdHostName column in dbc.logonoffv shows IP address rather than hostname when the hostname is tied to multiple IP addresses.
[SENTDO-3115][CS3199625] DSN trace log does not print the correct row count (which is a 64-bit integer) for SQLRowCount. It only shows the value of the lower order 4 bytes instead of the full 8 bytes.
20.00.00.035 —————————————————————–
Released 2025-10-24
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.035.
[SENTDO-2982] The DSN option useLocalCatalog option controls whether the connector includes catalog information in query results and metadata.
When set to N (default), catalog information is not included.
When set to Y, the connector includes the catalog name (for example, TD_LOCAL) in results returned to client applications.
This option allows users to choose whether their applications display catalog details when connecting through ODBC.
[SENTDO-3091] File descriptors were not all closed which can result in running out of file descriptors and being unable to open new files causing the connector to crash.
[SENTDO-3084] The first of multiple result sets generated by array parameter binding returns correct data while subsequent result sets contain extra trailing spaces in character columns, even when the table columns are defined with fixed CHAR lengths.
[SENTDO-3088] Resolved an issue where the connector did not route connections through the proxy when HTTPS_PROXY was provided.
[SENTDO-3094] The ODBC connector cannot connect to the database when Gateway mode is Require and SSLMode is Allow and DBCName is an URL with two cops.
[SENTDO-3095] TD ODBC connector crashes when DBCName is a FQDN (Fully Qualified Domain Name) and password is provided through TDWallet.
20.00.00.030 —————————————————————–
Released 2025-08-29
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.030.
[SENTDO-3037] TPT and ODBC co-existing in the same process may result in program crash in unix platforms.
[SENTDO-3071] Column LogonSource of dbc.logonoffv table should include the connector name (“ODBC”) and connector version number.
[SENTDO-3073] Data retrieval (SELECT queries) from database is 10 times slower when connected to TLS (443) port.
[SENTDO-3080] The connector fails to connect when using SSLMode Verify-CA and Verify-Full.
20.00.00.028 —————————————————————–
Released 2025-07-25
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.028.
[SENTDO-3043] When the user selects ClientTdHostName on logonoffv, the connector returns only the IP address, without the port number.
[SENTDO-3052] The connector fails to display Chinese characters in Teradata SQL Assistant.
[SENTDO-3059] When SSL Mode is set to ‘Require’, SQL Assistant and other GUI-based login applications experience login failures.
[SENTDO-3064] When the username or password is incorrect, the connector does not immediately return an error; instead, it waits until the connection attempt times out.
20.00.00.026 —————————————————————–
Released 2025-06-25
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.026.
[SENTDO-3038] Long connection latency.
[SENTDO-3049] LibCurl does not support Secure Transport on TLS 1.3.
[SENTDO-3051] Username, or UID, not allowed when using TD2 mechanism in multiple threads.
20.00.00.024 —————————————————————–
Released 2025-05-25
Resolved Issues
The following issues have been resolved in Simba Teradata ODBC Connector
20.00.00.024.
[SENTDO-2886] OIDC_LOGIN_HINT, OIDC_SCOPE and TOKEN_UID_CLAIM added in Token memory cache. The connector now added keys OIDC_LOGIN_HINT, OIDC_SCOPE and TOKEN_UID_CLAIM in the token memory cache. For more information, see the Installation and Configuration Guide.
[SENTDO-3040] The connector crashes when logging hex dump of received socket data. The connector will crash if
- Connection is using TLS; and
- Socket recv() failed; and
- Logging is set at TRACE (6) level.
[SENTDO-3045] The connector supports connecting to Vantage with TLS 1.3. The “SSL Protocol” setting that allows the user to select the SSL Protocol version they use to connect to the database now supports TLS 1.3 in addition to the already existing TLS 1.2.
20.00.00.022 —————————————————————–
Released 2025-04-25
Enhancements & New Features
[SENTDO-2887] Multiple Identities support
The connector now supports multiple identities OIDC_LOGIN_HINT, OIDC_PROMPT, and OIDC_TOKEN_CACHE in the token memory cache. For more information, see the Installation and Configuration Guide.
Resolved Issues
The following issue has been resolved in Simba Teradata ODBC Connector
20.00.00.022.
[SENTDO-2983] When TLS sockets fail, the connector does not catch the
SIGPIPE signal to prevent the application from crashing.This issue is resolved by the connector; however, if the application prefers to handle this signal, it can set the TD_NO_SIGPIPE_CATCH environment variable.
20.00.00.021 —————————————————————–
Released 2025-02-25
Enhancements & New Features
[SENTDO-2918] Enhanced proxy server Windows support
On Windows, the connector can now read from HTTP_PROXY, HTTPS_PROXY, and ALL_PROXY settings based on URI protocol. If URI protocol is:http://, HTTP_PROXY is used, if URI protocol is https://, HTTPS_PROXY is used, if both are unavailable, ALL_PROXY is used. For more information, see the Installation and Configuration Guide.
Resolved Issues
The following issue has been resolved in Simba Teradata ODBC Connector
20.00.00.021.
- [SENTDO-2803] When SSLMode is set to Allow and both TDMST and HTTPS ports are available, the connector uses the HTTPS port instead of returning an error message.
20.00.00.019 —————————————————————–
Released 2025-01-22
Enhancements & New Features
[SENTDO-2886] OIDC Token Memory Cache support
The connector can now reuse credentials and log in multiple times for short-lived connections without refreshing tokens. To do this, set the Disable Token Cache checkbox to No. For more information, see the Installation and Configuration Guide.
[SENTDO-2946] Enhanced data encryption support
You can now update the data encryption value from the connection string key UseDataEncryption to ClientAttributeEx in the database. For more information, see the Installation and Configuration Guide.
Resolved Issues The following issues have been resolved in Simba Teradata ODBC Connector 20.00.00.019.
[SENTDO-2879] In some cases, when using the EXTERNALBROWSER mechanism, the connector does not connect because a socket operation is blocking it.
[SENTDO-2934] If the SSO Browser window is cancelled or closed before connecting to the database, the connector hangs.
[SENTDO-2958] When SSLCRC is set to Require and either the OCSP certificate or the OCSP URI is unknown, the connection does not return to CRL.
20.00.00.018 —————————————————————–
Released 2024-12-26
Resolved Issues The following issues have been resolved in Simba Teradata ODBC Connector 20.00.00.018.
[SENTDO-2916] When binding data using SQL_C_WCHAR and setting the LC_ALL environment variable to ‘C’, the connector fails to return the data in UTF-8 format to the application.
[SENTDO-2941] The PERIOD(TIME(n)) does not get inserted when the DecimalDigits of SQLBindParameter is incorrect.
[SENTDO-2944] In the gateway session information, the certificate status is not updated.
[SENTDO-2945] When running a SELECT query with parameters, if the database does not figure out the type of an integral column (like INT or BIGINT), the connector wrongly assumes it is unsigned, causing a ‘numeric value out of range’ error.
[SENTDO-2949] The revocation function fails to check revocation because the revocation server is offline.
[SENTDO-2950] When the OCSP URI is missing in the database certificate, the connector continues to make OCSP requests.
[SENTDO-2951] When the username and password fields in the ODBC Administrator’s DSN are empty, SQLA terminates unexpectedly.
20.00.00.012 —————————————————————–
Released 2024-09-20
Resolved Issues The following issues have been resolved in Simba Teradata ODBC Connector 20.00.00.012.
[SENTDO-2876] The ‘abort’ button in SQL Assistant does not terminate the query.
[SENTDO-2899] When converting time, the connector converts the hour, minute, and second, but not the fractions of a second.
20.00.00.009 —————————————————————–
Released 2024
Enhancements & New Features
[SENTDO-2847] Enhanced TTU FIPS module
The connector uses the OpenSSL FIPS Provider module to make connections if the environment TTU_FIPS_ENABLE is set to the value “1”.
Resolved Issues The following issues have been resolved in Simba Teradata ODBC Connector 20.00.00.009.
[SENTDO-2870] The connector does not properly update the password in the OutConnectionString return value of a SQLDriverConnect() call when the password has expired in the database, or an administrator has forced a password change.
[SENTDO-2878] In the DSN Setup in ODBC Data Source Administrator of Windows, the Mechanism Options button is partially obscured if the pointer hovers over “Use Integrated Security”.
20.00.00.008 —————————————————————–
Released 2024-05-24
Enhancements & New Features
[SENTDO-2816] Client Credentials authentication
You can now authenticate your connection with Client Credentials, also known as Bearer Flow. To do this, from the Mechanism drop-down list select BEARER (set the MechanismName property to BEARER). For more information, see the Installation and Configuration Guide.
[SENTDO-2798] OIDC Device Authorization Grant authentication
You can now authenticate your connection with OIDC Device Authorization Grant, also known as OIDC Device Flow. To do this, from the Mechanism drop-down list select CODE (set the MechanismName property to CODE). For more information, see the Installation and Configuration Guide.
Resolved Issues The following issues have been resolved in Simba Teradata ODBC Connector 20.00.00.008.
[SENTDO-2813] When the client ID or scope value contains a space and it is not URL encoded, the connector truncates the value.
[SENTDO-2814] In some cases, when connecting to the Teradata database using SSLMode Prefer or Allow, the connector connects to an incorrect port.
[SENTDO-2844] When retrieving BIG5 characters (two bytes each) from a character set LATIN table’s VARCHAR column that has odd number of bytes (e.g. VARCHAR(25)), the first character of the next row is corrupted.
20.00.00.006 —————————————————————–
Released 2024-02-23
Resolved Issues The following issue has been resolved in Simba Teradata ODBC Connector 20.00.00.006.
- [SENTDO-2751] When a table contains a CLOB column size greater than 2,097,088,000 bytes, .NET System.Data.Odbc.OdbcDataReader.GetSchemaTable() returns arithmetic overflow exception.
20.00.00.005 —————————————————————–
Released 2024-01-25
Resolved Issues The following issue has been resolved in Simba Teradata ODBC Connector 20.00.00.005.
- [SENTDO-2751] When a table contains a CLOB column size greater than 2,097,088,000 bytes, .NET System.Data.Odbc.OdbcDataReader.GetSchemaTable() returns arithmetic overflow exception.
==============================================================================