When you try to do a parallel load of a Teradata table into SAS^® Cloud Analytic Services (CAS), parts of the query that could be passed might not be passed to Teradata. Instead of Teradata doing the processing, the processing of the query is done after the data is read into CAS. However, the data is still being loaded into CAS in parallel. This issue might occur when the following is true:

• Your CASLIB statement includes both the DATABASE= and SCHEMA= options, where the DATABASE= option points to the user's database and the SCHEMA= option points to the database in which the tables being queried are located.
• You are using FedSQL and your query includes one or more of the following:
  • the DISTINCT keyword
  • summary functions with a GROUP BY clause
  • joins
  • the WHERE clause

If your query includes syntax that is valid in SAS but that is not supported by the database, it is expected that the syntax will not be included in the query that is passed to Teradata.

Here are some workarounds:

• Use DATATRANSFERMODE=serial.
• Create a view in the user's database that is a query of the table in the other database. Instead of including both DATABASE= and SCHEMA=, include only DATABASE= pointing to your database in the CASLIB statement.

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