A new update is available for SAS/ACCESS Interface to Teradata , version 9.47 :
SAS Note 66794 | A WHERE clause for a Teradata BIGINT column generates the message \"...Precision error in FLOAT type constant or during implicit conversions...\" |
SAS Note 68314 | SYSDESC, SYSNAME, and SYSVALUE variables might be blank when using SASHELP.VLIBNAM or DICTIONARY.LIBNAME dictionary tables against a Teradata library |
SAS Note 68644 | Accessing Teradata 16.00 or later results in \"Row size exceeds 64K bytes...incompatible with the Client software\" when you use certain procedures |
SAS Note 68698 | Trying to insert data into an existing Teradata table might result in errors when table variable names contain more than 32 characters |
SAS Note 69350 | SAS® 9.4M7 (TS1M7) might generate \"ERROR: Teradata connection: CLI2: BADBUFRQ(302): Invalid buffer size\" when querying a Teradata table |
SAS Note 69491 | Trying to connect to Teradata using LDAP might result in logon failure |
SAS Note 69574 | Trying to read in a Teradata table that contains a variable defined as a DATE data type might generate a conflicting data type error |
SAS Note 70928 | SAS/ACCESS® Interface to Teradata support for Teradata Tools and Utilities (TTU) 17.20 and later in AIX environments |
This list of notes might be incomplete. For a complete list of issues addressed by this hot fix, visit the hot fix page for N6F001 |
Note: A comprehensive list of all SAS hot fixes is available from support.sas.com. You can use the SAS Hot Fix Analysis, Download, and Deployment (SASHFADD) tool to manage your SAS hot fixes.
Catch the best of SAS Innovate 2025 — anytime, anywhere. Stream powerful keynotes, real-world demos, and game-changing insights from the world’s leading data and AI minds.