15 TERADATA

============================================================================== Simba Teradata ODBC Driver with SQL Connector Release Notes ==============================================================================

The release notes provide details of enhancements, features, known issues, and workflow changes in Simba Teradata ODBC Driver 17.00.00.1022, as well as the version history.

17.00.00.1022 ================================================================

Released 2020-12-29

Enhancements & New Features

  • Internal driver improvements

    The driver has been updated with minor internal improvements.

Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.

  • Some custom fields are not supported for SQLGetDescField.

    When calling SQLGetDescField, the driver 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 driver 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 driver 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 driver 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 driver.

17.00.00.004 —————————————————————–

  • Improved security for credentials in DSNs

    Beginning with this release, the driver does not allow passwords and authentication parameters to be specified as-is and then saved into DSNs. If you have saved a password or authentication parameter in a DSN that you configured previously, the driver ignores those values when connecting to the database. Instead, the driver prompts you to specify those values at connection time.

    If you want to continue saving your database credentials in the DSN so that you are not required to specify your credentials every time you connect to the database, then do the following:

    1. Use Teradata Wallet to map your password and authentication parameters to reference strings.

    2. Specify and save those reference strings in your DSN:

      • To specify the reference string for your password, use the Password Wallet String field (or the Password connection property).
      • To specify the reference string for your authentication parameters, use the Parameter Wallet String field (or the AuthenticationParameter connection property).

    For more information, see the Installation and Configuration Guide.

Version History ==============================================================

17.00.00.020 =================================================================

Released 2020-11-25

Enhancements & New Features

  • [SENTDO-2030] Fallback support for FastExport

    When the driver attempts to execute a query using the FastExport protocol and the query fails, the driver now attempts to execute the query using the standard protocol.

  • [SENTDO-1948] Solaris updates

    On Solaris Sparc and Solaris x86, the driver is now built using Solaris Studio 12.6.

Resolved Issues The following issue has been resolved in Simba Teradata ODBC Driver 17.00.00.020.

  • [SENTDO-2021] In some cases, when the driver uses the FastExport protocol to retrieve query results from a database that contains a large number of AMPs, the driver attempts to create more connections to the database than the database can handle, and hangs or terminates unexpectedly.

    This issue has been resolved. Now the driver does not create more than 8 connections to retrieve data.

17.00.00.019 —————————————————————–

Released 2020-10-25

Enhancements & New Features

  • [SENTDO-1961] Documentation for Return Output Paramaters As Result Set

    The driver Help files now include documentation for the Return Output Paramaters As Result Set feature.

Resolved Issues The following issues have been resolved in Simba Teradata ODBC Driver 17.00.00.019.

  • [SENTDO-1913] If multiple statements are separated by a semicolon (;) and at least one statement contains a LOB column retrieval, the driver returns an error.

  • [SENTDO-1926] If a value is specified as NULL in SQLBindParameter for data of type SQL_C_DOUBLE or SQL_C_FLOAT, the database returns an error.

  • [SENTDO-1947] The driver incorrectly trims trailing spaces in strings.

  • [SENTDO-1951] In some cases, when a query involves BINARY data, the driver’s performance is decreased.

  • [SENTDO-1952] If a catalog name is specified, the driver does not properly execute SQLTables requests, even when Use Null For Catalog Name is selected.

  • [SENTDO-1956] When the driver reads a CHAR(n) column that uses the KANJISJIS or UNICODE character set and the value contains only spaces, the driver hangs.

  • [SENTDO-2000] In some cases, when the AMPs (Access Module Processors) decline the FastExport protocol, the driver returns an error.

    This issue has been resolved. The driver now ignores any AMPs that decline the FastExport protocol.

17.00.00.018 —————————————————————–

Released 2020-07-24

Enhancements & New Features

  • [SENTDO-1852] Windows GUI option to return output parameters as result set

    On Windows, you can now use the DSN Configuration dialog box to configure the driver to return output parameters as a result set. To do this, select the Return Output Parameters As Result Set check box. For more information, see the Installation and Configuration Guide.

  • [SENTDO-1861] SQLSpecialColumns optimization

    When SQLSpecialColumns retrieves the optimal set of columns that uniquely identifies a row in a table, it now retrieves only the primary index. Previously, SQLSpecialColumns retrieved both the primary and secondary indexes.

  • [SENTDO-1901] Encrypted password support

    In response to a SQLDriverconnect request, the driver now returns encrypted passwords encoded in hexadecimal with the key PASSWORD_X.

Resolved Issues The following issues have been resolved in Simba Teradata ODBC Driver 17.00.00.018.

  • [SENTDO-1809] When SQLBindParameter is called before SQLPrepare, the driver uses incorrect values for the data type, length, and decimal digits.

  • [SENTDO-1827] In some cases, SQL queries that include a WHERE clause containing Hebrew characters might not fetch any data.

  • [SENTDO-1889] When the driver performs SQLStatistics against a table that contains more than 2,147,483,647 rows, the database returns an error.

  • [SENTDO-1905] When a stored procedure with input parameters returns a database error, the driver terminates unexpectedly.

17.00.00.017 —————————————————————–

Released 2020-05-22

Enhancements & New Features

  • [SENTDO-1571] Return output parameters as result set

    You can now configure the driver to return output parameters as a result set. To do this, set the OutputAsResultSet connection property to 1. For more information, see the Installation and Configuration Guide.

  • [SENTDO-1806] Support for enhanced stored procedure names

    The driver now supports stored procedures whose names include dot notation and back-ticks (`).

Resolved Issues The following issues have been resolved in Simba Teradata ODBC Driver 17.00.00.017.

  • [SENTDO-1741] In some cases, the driver terminates unexpectedly with an out of memory error.

  • [SENTDO-1818] 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.

  • [SENTDO-1824] 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.

  • [SENTDO-1830] Database error messages that include Japanese characters are displayed as unreadable characters.

17.00.00.016 —————————————————————–

Released 2020-04-24

Enhancements & New Features

  • [SENTDO-1795] Support for macOS 10.15

    The driver now supports macOS 10.15 “Catalina”.

  • [SENTDO-1747] Built with Xcode 10.2.1

    On macOS, the driver is now built with Xcode 10.2.1.

  • [SENTDO-1754] Support for RHEL 8

    The driver now supports Red Hat Enterprise Linux (RHEL) 8.

  • [SENTDO-1775] Support for Oracle Enterprise Linux 8

    The driver now supports Oracle Enterprise Linux 8.

Resolved Issues The following issues have been resolved in Simba Teradata ODBC Driver 17.00.00.016.

  • [SENTDO-1458] The driver does not read the values in the [ODBC] section of the odbc.ini configuration file.

  • [SENTDO-1569] 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.

  • [SENTDO-1771] In some multithreaded executions, the internal storage session number is corrupted.

  • [SENTDO-1777] If you are using the UTF-8 character set and you create a table column with CHARACTER SET KANJISIS, then call SQLBindCol to SQL_C_WCHAR, and then call SQLFetchScroll, only a part of the data is displayed.

    This issue has been resolved. Now, the driver displays all data up to the maximum EXPORTWIDTH setting for the database.

  • [SENTDO-1808] 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.

17.00.00.015 —————————————————————–

Released 2020-02-25

Enhancements & New Features

  • [SENTDO-1735] Improved performance during connection time

    When connecting to the database, the driver can now detect and use the transaction isolation level that is configured on the database by default. Before, the driver sent a request to set the transaction isolation level for each connection.

  • [SENTDO-1743] Support for notarization

    The driver now supports notarization on macOS systems, enabling it to be run on macOS versions 10.14.6 and later.

Resolved Issues The following issues have been resolved in Simba Teradata ODBC Driver 17.00.00.015.

  • [SENTDO-1767] When the driver returns the NUMBER value “0” using a string data type such as CHARACTER, the returned value uses an incorrect precision.

  • [SENTDO-1765] The driver uses inconsistent names for some connection properties.

    This issue has been resolved. Before, various components in the driver used different names to refer to these properties:

    • AccountString or AccountStr
    • NoHelpDatabase or DontUseHelpDatabase

    The driver now consistently uses AccountStr and DontUseHelpDatabase as the names of these properties. For more information, see the Installation and Configuration Guide.

    Note: “Account” continues to be accepted as an alias for the AccountStr property.

  • [SENTDO-1761] On Windows and macOS, the Driver Options dialog box displays an incorrect default value for the Reconnect Interval option.

  • [SENTDO-1748] 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.

  • [SENTDO-1745] When querying interval data, if the application sets a precision that is greater than 2, the driver returns an “Interval Field Overflow” error.

  • [SENTDO-1733] When retrieving an empty column using a buffer with a length of 0, the driver does not return the expected truncation warning for the null terminator.

  • [SENTDO-1707] When converting data from one type to another, if the length of the metadata is greater than the column size, the driver returns a truncation error.

17.00.00.012 —————————————————————–

Released 2019-11-25

Enhancements & New Features

  • [SENTDO-1704] Updated driver version information in Linux binary

    You can now check the Linux driver’s version from the driver binary file. To do this, open the .so file in a text editor, and search for the text “\(driver_version_sb\):”. The driver’s version number is listed after this text.

  • [SENTDO-1680] Prefixes for log file names

    The driver now includes a prefix in the names of the log files that are generated when logging is enabled. The prefix includes the user name associated with the connection and the process ID of the application through which the connection is made.

  • [SENTDO-1678] Improvements for logging level 6 (TRACE)

    The log messages that the driver generates when logging is enabled at level 6 (TRACE) have been updated to be more detailed and precise. This includes improvements such as providing more accurate descriptions of socket errors and session IDs.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 17.00.00.012.

  • [SENTDO-1695] 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.

  • [SENTDO-1657] When using the driver in an ADODB application, if you try to retrieve an empty string, the driver returns an error.

  • [SENTDO-1630] 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.”

  • [SENTDO-1460] In some cases, when converting a Thai language character from UTF-8 encoding to another encoding type, the driver reports a truncation error.

  • [SENTDO-1562][SENTDO-1617] Setting the Enable Redrive option to “Default” (EnableRedrive=DEFAULT) is equivalent to enabling the property (EnableRedrive=Yes).

    This issue has been resolved. When this property is set to “Default”, the driver now determines whether or not to use Redrive based on the configuration of the database.

17.00.00.010 —————————————————————–

Released 2019-09-25

Enhancements & New Features

  • [SENTDO-1163] FastExport support

    The driver now supports the FastExport feature from Teradata Database. The FastExport protocol improves the performance of SELECT statements that meet certain criteria. For more information, see the Installation and Configuration Guide.

  • [SENTDO-1443] Native Object Store (NOS) Support

    The driver now supports the use of the NOS feature from Teradata Database. For more information, see the Teradata Database documentation.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 17.00.00.010.

  • [SENTDO-1608] In some cases, when two or more connections are created at the same time, the driver terminates unexpectedly.

  • [SENTDO-1591] In some cases, when you select and expand a view containing characters that are not ASCII-compatible, the driver returns an error.

  • [SENTDO-1557] 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.

    This issue has been resolved. The driver has been updated to return INTERVAL data types as strings. For more information, see “DateTime and Interval Data Types” in the Teradata Vantage Data Types and Literals documentation: https://docs.teradata.com/reader/~_sY_PYVxZzTnqKq45UXkQ/r97F2MpxK2V0V_hsvuJdNA.

  • [SENTDO-1543] When using a prepared statement to call a stored procedure that contains CLOB output parameters, the driver returns an error.

  • [SENTDO-1539] The connection timeout behavior in the driver does not work as expected, and does not use the timeout period specified by SQL_ATTR_CONNECTION_TIMEOUT.

  • [SENTDO-1605] When the Enable Extended Statement Information option (or the EnableExtendedStmtInfo property) is disabled, the driver returns an incorrect DBC type for a data type.

  • [SENTDO-1563] When the Enable Extended Statement Information option (or the EnableExtendedStmtInfo property) is disabled, some cells in the DBC.DBQLogTbl table display as “”.

  • [SENTDO-1527] The driver cannot insert TIMESTAMP parameter data that contains fractional digits.

  • [SENTDO-1650] When LATIN1252_30A is used as the character set for the session, the driver does not return the euro symbol (€) correctly.

  • [SENTDO-1642] When converting a value from TIMESTAMP to SQL_TYPE_TIMESTAMP, the driver truncates the fractional digits from the seconds field.

  • [SENTDO-1553] SQLDescribeCol() and SQLColAttributes() return incorrect column sizes for CURRENT TIMESTAMP(n) columns.

17.00.00.007 —————————————————————–

Released 2019-07-25

Enhancements & New Features

  • [SENTDO-1574] Updated ICU version

    The driver now uses ICU version 58.2.x.

  • [SENTDO-1513] Updated support for interval, time zone, and XML data types

    You can now configure the driver to return these data types as SQL_WLONGVARCHAR instead of the default SQL types, which map more closely to the Teradata data type but may not be supported in .NET applications. To do this, configure the new IntervalPeriodTypesToString connection property. For more information about this property and a complete list of the applicable data types, see the Installation and Configuration Guide.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 17.00.00.007.

  • [SENTDO-1544] In some cases, when converting a floating point number to a string data type, a truncation error occurs.

    This issue has been resolved. To prevent this truncation error, the driver has been updated to always return the converted values in a decimal format instead of an exponent format.

  • [SENTDO-1555] 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.

    This issue has been resolved. The driver now logs the issue, but connects to the database successfully.

  • [SENTDO-1561] 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.

  • [SENTDO-1562] In some cases, when the Enable Redrive option is set to “Default” (EnableRedrive=REDRIVE_DEFAULT), the driver fails to run queries.

    As an interim workaround, the driver has been updated to treat the Default (or REDRIVE_DEFAULT) setting as being equivalent to this property being enabled, instead of attempting to detect whether or not the Redrive feature is enabled on the server.

  • [SENTDO-1597] In some cases, applications on Linux might have problems accessing the dynamically linked libraries that are used by the driver.

    This issue has been resolved. On Linux, the third-party libraries are now statically linked.

17.00.00.005 —————————————————————–

Released 2019-06-25

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 17.00.00.005.

  • [SENTDO-1533] Driver logs do not include error messages about string truncation.

  • [SENTDO-1541] The driver cannot parse queries that contain carriage return characters (.

    This issue has been resolved. The driver now replaces carriage return characters with spaces, and parses these queries successfully.

  • [SENTDO-1551] The driver does not allow queries of empty strings.

==============================================================================