If you enable the Oracle sqlnet.ora configuration option TRACE_LEVEL_CLIENT, your SAS^® session might abort when you disconnect from Oracle. This behavior can occur when all the following are true:

• Your Oracle client is version 19. 
• Your Oracle server is version 19.
• The sqlnet.ora option TRACE_LEVEL_CLIENT is set to a value other than OFF or 0.
• You are running the SAS^® 9.4M6 (TS1M6) or SAS^® 9.4M7 (TS1M7) release, and you take one of these actions:
  • Clear an Oracle library name.
  • Use an explicit SQL query to connect to Oracle. The error then occurs after the DISCONNECT or QUIT statement.
  • End your SAS session.

Depending on how you are running SAS, these errors might appear in the console:

The SAS exit code is 0, and the SAS log typically does not indicate any errors. However, the full SAS program might not have executed. See also SAS Note 68859, "A 'SAS WTABORT' error occurs, and a SAS^® session ends unexpectedly, but the SYSCC code is 0."

The only workaround is to set the TRACE_LEVEL_CLIENT option to OFF.

This problem is not due to any issue with SAS but has been reported to Oracle, because the same behavior can be replicated outside of SAS. The Oracle bug ID for this issue is 33613169.

Operating System and Release Information