The fedSql.execDirect CAS action fails to stop writing data when the CAS_DISK_CACHE location is out of space. When that occurs, the SAS^® Cloud Analytic Services (CAS) server logs can grow to very large sizes and fill the log file system. In order to stop the log growth, an administrator needs to kill the CAS session processes that are running the failing fedSql.execDirect action.

Repeating errors like the following might appear in the CAS log:

This error indicates that the CAS_DISK_CACHE location (/sastmp/cascache, in this example) is out of space. If this error resulted from the fedSql.execDirect action, the error might continue to be written to the log indefinitely and cause abnormal log file growth. However, this error alone does not indicate the problem that is resolved by the hot fix in this note. Instead, the repeated instances of the error, caused by a running fedSql.execDirect action, are an indication of this problem.

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