Resolved issues track corrections and updates to Teradata Tools and Utilities software and to documentation affected by the updates.
| Issue | Description |
|---|---|
| SENTDO-1755 | In specific cases, when using UTF-8 as the session character set and retrieving data that uses the KANJISJIS character set, the driver returns incorrect data. This issue has been resolved. Before, the following scenario would cause the driver to use an incorrect column length when returning data:
The driver is now able to retrieve the data correctly. |
| TDS-216 | SQLDescribeCol() and SQLColAttributes() return incorrect column sizes for CURRENT TIMESTAMP(n) columns. |
| TDS-225 | The driver does not read the values in the [ODBC] section of the odbc.ini configuration file. |
| TDS-228 | In some cases, when converting a Thai language character from UTF-8 encoding to another encoding type, the driver reports a truncation error. |
| TDS-261 | If you are using LDAP authentication and a user name or password contains a space or a quotation mark ( " ), the driver returns an error. This issue has been resolved. The driver now encloses user names and passwords in quotation marks before sending them to the server. In addition, if a password contains a quotation mark, the quotation mark is replaced with two quotation marks before being sent to the server. |
| TDS-268 | When the Enable Extended Statement Information option (or the EnableExtendedStmtInfo property) is disabled, some cells in the DBC.DBQLogTbl table display as "<Error>". |
| TDS-269 | The driver cannot insert TIMESTAMP parameter data that contains fractional digits. |
| TDS-274 | When using a prepared statement to call a stored procedure that contains CLOB output parameters, the driver returns an error. |
| TDS-275 | The driver cannot parse queries that contain carriage return characters (\r). ODBC Driver for Teradata now replaces carriage return characters with spaces, and parses these queries successfully. |
| TDS-280 | If the driver fails to retrieve the name of the user account that is currently logged into the client machine, then the driver returns SQL_ERROR and the connection fails. The driver now logs the issue, but connects to the database successfully. |
| TDS-283 | The driver does not allow queries of empty strings. |
| TDS-285 | When attempting to retrieve a field descriptor with an identifier value that is between 1300 to 1399 (inclusive), the driver returns an "invalid descriptor field" error. |
| TDS-286 | When connected to a Teradata Database 16.20 instance, and INTERVAL data types are bound to the SQL_C_BINARY type, the driver cannot query INTERVAL data. |
| TDS-288 | Driver logs do not include error messages about string truncation. |
| TDS-289 | In some cases, when you select and expand a view containing characters that are not ASCII-compatible, the driver returns an error. |
| TDS-292 | Setting the Enable Redrive option to "Default" (EnableRedrive=DEFAULT) is equivalent to enabling the property (EnableRedrive=Yes). |
| TDS-293 | In some cases, applications on Linux might have problems accessing the dynamically linked libraries that are used by the driver. On Linux, the third-party libraries are now statically linked. |
| TDS-295 | In some cases, when two or more connections are created at the same time, the driver terminates unexpectedly. |
| TDS-297 | On big-endian platforms such as AIX or HP-UX, when you try to run a "SELECT current_date" query, the driver returns the following error message: "Conversion from number to string failed due to undersized character buffer." |
| TDS-303 | When LATIN1252_30A is used as the character set for the session, the driver does not return the euro symbol (€) correctly. |
| TDS-304 | When selecting an empty column, if you provide a buffer length of 0 in the SQLGetData call, the driver does not return the expected truncation warning. |
| TDS-311 | When you try to run a CREATE PROCEDURE or REPLACE PROCEDURE command, if the "CREATE" or "REPLACE" part of the command is immediately followed by a tab character, the driver returns a syntax error. |
| TDS-321 | In some cases, the driver terminates unexpectedly with an out of memory error. |
| TDS-322 | When querying interval data, if the application sets a precision that is greater than 2, the driver returns an "Interval Field Overflow" error. |
| TDS-325 | When the database cannot infer the type of a parameter marker in a SQLDescribeParam() call, the driver returns a parameter size of 0. This issue has been resolved. In this scenario, the driver now calculates a parameter size by dividing 64000 by the number of parameter markers. |
| TDS-329 | When the driver returns the NUMBER value "0" using a string data type such as CHARACTER, the returned value uses an incorrect precision. |
| TDS-333 | In some multithreaded executions, the internal storage session number is corrupted. |
| TDS-349 | If you create a table with a NOT NULL column, the Null indicator of the result set that is returned from a MACRO is always set to SQL_NULLABLE=1. |
| TDS-351 | When an application inserts rows that include LOB columns, and one row fails with an error such as "duplicate unique primary key", error, the subsequent inserts return various other errors. This issue has been resolved. The driver now has better Teradata database error handling when executing parameterized insert queries with LOB data. |
| TDS-352 | If multiple errors occur during a session, for each error the driver displays all the previously displayed error messages from the session. This issue has been resolved. The driver now only displays the error message for the most recent error. |
| TDS-356 | Database error messages that include Japanese characters are displayed as unreadable characters. |