If the value of the SCHEMA= option or the DATABASE= option for a DBMS library differs from that of the value for the USERID= option, the DBMSTEMP tables are not deleted when you execute the SCD2 code. As a result, that code will fail the next time you attempt to run it (in the same session or subsequent sessions). When the code fails, the following error message is generated:

ERROR: The ORACLE table <TEMP_NAME> has been opened
for OUTPUT. This table already exists, or there is a name
conflict with an existing object. This table will not be
replaced. This engine does not support the REPLACE option.

The solution is to omit the SCHEMA= option or the DATABASE= option from the ETLSTMP library allocation. This action prevents the schema or database information from being included in the DATASETS procedure; therefore, the software will find and delete the tables.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at: