The Teradata Loader transformation generates code that will not be passed to the database for execution. The transformation uses the data set option DBCREATE_TABLE_OPTS to specify DBMS-specific clauses when the Teradata table is created in the database. For example, if your source table contains a primary index, the Teradata Loader transformation will use the DBCREATE_TABLE_OPTS data set option to generate the DBMS-specific clause to build a primary index when the target table is created. The Teradata Loader transformation also uses the option during the insertion of new records into the target table. Because the option is valid only when processing statements that create a table, the generated statements are not passed directly to the database for processing. With the SAS^® DBMS tracing options invoked, you will see the following message in the SAS log:

  SAS_SQL:  Cannot handle dataset options.
  SAS_SQL:  Unable to convert the query to a DBMS specific SQL statement due to an
            error.

The only workaround for the issue is to modify the code that is generated by the Teradata Loader transformation to remove the DBCREATE_TABLE_OPTS data set option from the INSERT statement.

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

Operating System and Release Information

A fix for this issue for SAS Data Integration Studio 4.6 is available at:

A fix for this issue for SAS Data Integration Studio Server Data 4.6 is available at: