SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem 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

DetailsHotfixAboutRate It

When you run code that accesses a Teradata database version 16.00 or later, and results generate a row size that exceeds 64,000 bytes, the following error occurs:

ERROR: General error Response Row size exceeds 64K bytes and is incompatible with the Client software. 

Prior to Teradata Tools and Utilities (TTU) 16.0 and Teradata Server 16.00, 64K was the hard limit of the response parcel.

Teradata 16.00 and later releases support response row sizes up to 1 MB.

The only workaround is to restrict the number of columns to avoid exceeding the 64K row size.

Beginning with SAS® 9.4M7 (TS1M7) and SAS® Viya®, the DS2, FEDSQL, and CAS procedures support this new Teradata feature. See SAS Note 63395, "Accessing Teradata version 16.00 or later might result in 'General error Response Row size exceeds 64K bytes...incompatible with the Client software.'"  

However, the DATA step, and other procedures, like the SQL procedure, including Explicit SQL, can still receive the error for wide-row tables.

Click the Hot Fix tab in this note to access the hot fix for this issue.

After the hot fix is installed, support is automatically enabled: 

  • SAS/ACCESS® Interface to Teradata queries the Teradata server and the TTU client to determine whether the 1-MB row size is configured.
  • If the 1-MB row size is configured, SAS/ACCESS Interface to Teradata automatically uses it, except when using any of the Teradata legacy utility stand-alone features, such as FastLoad, MultiLoad, Multistatement, and FastExport.   
  • However, since TPT=YES is enabled by default, SAS/ACCESS Interface to Teradata can take advantage of the 1-MB row size automatically as well, because FastLoad, MultiLoad, Multistatement, and FastExport actions with TPT take full advantage of 1-MB support.

To disable support for 1-MB response row sizes, you can take the following actions:

  • Set an environment variable:

       export TD_1MB_ROW=OFF
     
  • Start SAS® with the SET option:

       sas -set TD_1MB_ROW OFF -otherOptions
     
  • Use a SAS OPTIONS statement:

       options set = TD_1MB_ROW OFF;

To determine whether support is enabled or not, run the following OPTIONS statement with a valid Teradata library name:

options sastrace="d," sastraceloc=saslog nostsuffix ;
libname libref teradata user=user pass=password server=server ;

If support is enabled, the SASTRACE output includes the following:

TERADATA: Server Supports 1MB response buffer.
TERADATA: TD_1MB_ROW = ON

If support is disabled, and you attempt to access a wide-row Teradata table, the SASTRACE output includes the following:

TERADATA: Server Supports 1MB response buffer.
TERADATA: TD_1MB_ROW = OFF
ERROR: Teradata row not delivered (trget): Response Row size exceeds 64K
       bytes and is incompatible with the Client software.

SAS/ACCESS Interface to Teradata on z/OS (mainframe) does not support a 1-MB row size.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS/ACCESS Interface to TeradataMicrosoft® Windows® for x649.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8 Enterprise 32-bit9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8 Enterprise x649.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8 Pro 32-bit9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8 Pro x649.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8.1 Enterprise 32-bit9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8.1 Enterprise x649.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8.1 Pro 32-bit9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 8.1 Pro x649.459.489.4 TS1M59.4 TS1M8
Microsoft Windows 109.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 20089.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 2008 R29.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 2008 for x649.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 2012 Datacenter9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 2012 R2 Datacenter9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 2012 R2 Std9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 2012 Std9.459.489.4 TS1M59.4 TS1M8
Microsoft Windows Server 20169.459.489.4 TS1M59.4 TS1M8
Windows 7 Enterprise 32 bit9.459.489.4 TS1M59.4 TS1M8
Windows 7 Enterprise x649.459.489.4 TS1M59.4 TS1M8
Windows 7 Home Premium 32 bit9.459.489.4 TS1M59.4 TS1M8
Windows 7 Home Premium x649.459.489.4 TS1M59.4 TS1M8
Windows 7 Professional 32 bit9.459.489.4 TS1M59.4 TS1M8
Windows 7 Professional x649.459.489.4 TS1M59.4 TS1M8
Windows 7 Ultimate 32 bit9.459.489.4 TS1M59.4 TS1M8
Windows 7 Ultimate x649.459.489.4 TS1M59.4 TS1M8
64-bit Enabled AIX9.459.489.4 TS1M59.4 TS1M8
64-bit Enabled Solaris9.459.489.4 TS1M59.4 TS1M8
HP-UX IPF9.459.489.4 TS1M59.4 TS1M8
Linux for x649.459.489.4 TS1M59.4 TS1M8
Solaris for x649.459.489.4 TS1M59.4 TS1M8
SAS SystemSAS Data Connector to TeradataLinux for x64V.03.03Viya
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.