Problem Note 68214: Trying to save a CAS table into Teradata might result in the table being created in an unexpected database
 |  |  |  |  |
If you try to save a SAS® Cloud Analytic Services (CAS) table into Teradata, the Teradata table might be created in the default database when the following conditions exist:
- You specify the DATATRANSFERMODE=PARALLEL option.
- You specify the DATABASE= option for your default database for the user's connection to Teradata.
- You specify the SCHEMA= for the database that you read from and in which you want to create the table with the SAVE action.
- The database is different for the DATABASE= and SCHEMA= options.
- You run SAS® Viya® 3.5 with June 09, 2021 or later hot fixes installed.
Rather than the table being created in the database referenced by the SCHEMA= option, the table is created in the database referenced by the DATABASE= option under these conditions. You are unable to do anything with the newly created table using the same CASLIB because the table is locked for the database referenced by the SCHEMA= option.
The workaround is use DATATRANSFERMODE=SERIAL.
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
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Data Connect Accelerator for Teradata | Linux for x64 | V.03.05 | Viya | Viya | |
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
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.5&softwareContextId=softwareUpdates| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2024-07-05 12:43:11 |
| Date Created: | 2021-08-05 10:39:45 |