Loading a DBMS table into SAS Cloud Analytic Services (CAS) might take longer than expected or fail to complete when you use the following data connector options in your CASLIB:

• SCANSTRINGCOLUMNS=TRUE
• NUMREADNODES=0 (or greater than 1)

The problem occurs when loading Teradata tables, but the issue might also occur with other data connectors.

The implementation of SCANSTRINGCOLUMNS=true for SAS^® Data Connector to Teradata was not intended for use when NUMREADNODES is not 1. In addition, there is not any expected performance benefits when you use both data connector options.

Your database administrator might report the unexpected behavior, or you might observe it in the driver trace outputs, which are available by adding the following options to your CASLIB:

A DRIVER SQL SELECT clause is displayed in each CAS log. This clause contains a MAX(LENGTH("column-name")) for each VARCHAR column. This clause should appear only in the CAS head node log, but this clause also occurs in each of the CAS node logs that are referenced by DRIVER_TRACEFILE, which informs you that it ran on every CAS Node.

Workarounds 

To circumvent this issue, complete any of the following workarounds: 

• Use SCANSTRINGCOLUMNS=TRUE with NUMREADNODES=1.
• Use SCANSTRINGCOLUMNS=FALSE with NUMREADNODES=0 or more than 1.
• Implement parallel data transfer where you must license SAS^® In-Database Technologies, and your SAS administrator must deploy SAS^® Embedded Process.

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.

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