| J8F008 for 64-bit Enabled AIX |
| SAS/ACCESS Interface to Teradata 9.47 |
| Issue(s) Addressed: | Introduced: |
| 66794 | A WHERE clause for a Teradata BIGINT column generates the message "...Precision error in FLOAT type constant or during implicit conversions..." |
J8F001 |
| 68314 | SYSDESC, SYSNAME, and SYSVALUE variables might be blank when using SASHELP.VLIBNAM or DICTIONARY.LIBNAME dictionary tables against a Teradata library |
J8F002 |
| 68644 | Accessing Teradata 16.00 or later results in "Row size exceeds 64K bytes...incompatible with the Client software" when you use certain procedures |
J8F003 |
| 68698 | Trying to insert data into an existing Teradata table might result in errors when table variable names contain more than 32 characters |
J8F004 |
| 69350 | SAS® 9.4M7 (TS1M7) might generate "ERROR: Teradata connection: CLI2: BADBUFRQ(302): Invalid buffer size" when querying a Teradata table |
J8F005 |
| 69491 | Trying to connect to Teradata using LDAP might result in logon failure |
J8F006 |
| 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 |
J8F007 |
NOTE: Customers running AIX 7.2 who wish to install the hot fix for TTU 17.20 must install hot fix N6F001 instead.
NOTE: If you install this hot fix, you must also install hot fixes I9R144 and I9R026 for Base SAS 9.4_M7. |
|
| N6F001 for 64-bit Enabled AIX |
| SAS/ACCESS Interface to Teradata 9.47 |
| Issue(s) Addressed: | Introduced: |
| 66794 | A WHERE clause for a Teradata BIGINT column generates the message "...Precision error in FLOAT type constant or during implicit conversions..." |
N6F001 |
| 68314 | SYSDESC, SYSNAME, and SYSVALUE variables might be blank when using SASHELP.VLIBNAM or DICTIONARY.LIBNAME dictionary tables against a Teradata library |
N6F001 |
| 68644 | Accessing Teradata 16.00 or later results in "Row size exceeds 64K bytes...incompatible with the Client software" when you use certain procedures |
N6F001 |
| 68698 | Trying to insert data into an existing Teradata table might result in errors when table variable names contain more than 32 characters |
N6F001 |
| 69350 | SAS® 9.4M7 (TS1M7) might generate "ERROR: Teradata connection: CLI2: BADBUFRQ(302): Invalid buffer size" when querying a Teradata table |
N6F001 |
| 69491 | Trying to connect to Teradata using LDAP might result in logon failure |
N6F001 |
| 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 |
N6F001 |
| 70928 | SAS/ACCESS® Interface to Teradata support for Teradata Tools and Utilities (TTU) 17.20 and later in AIX environments |
N6F001 |
NOTE: This hot fix is only appropriate for customers running AIX 7.2 to support TTU 17.20. All other customers must install hot fix J8F008 instead.
NOTE: If you install this hot fix, you must also install hot fixes I9R026 and I9R144 for Base SAS 9.4_M7. |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes