If you try to read in a Teradata table, an error similar to the following might occur:

The error might occur when the following is true:

• The Teradata table contains at least one variable that is defined as a DATE data type.
• You use the LIBNAME Teradata engine.
• The LIBNAME or the data set option FASTEXPORT= is set to YES.
• The LIBNAME or the data set option CAST= is set to YES. Or, the option is not specified and SAS determines that the data expansion is less than the CAST_OVERHEAD_MAXPERCENT= option setting.
• The LIBNAME or data set option TPT= is either set to YES or is not specified since YES is the default.

The workarounds for this issue include the following:

• Use CAST=NO. This workaround is not an option if the Teradata table contains a variable defined as a DECIMAL data type. This variable causes a different conflicting data type error for the decimal column. For more information, refer to SAS Note 61632, "The "Conflicting data length..." error occurs when you use SAS/ACCESS^® Interface to Teradata with Teradata 15.10 and 16 clients."
• Use TPT=NO. This option might cause slower performance depending on the amount of data that is read into SAS from Teradata.
• Use explicit pass-through rather than the LIBNAME statement. 

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

Operating System and Release Information

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at

A fix for this issue for SAS/ACCESS Interface to Teradata 9.47 is available at:

A fix for this issue for SAS/ACCESS Interface to Teradata 9.46 is available at: