A problem might occur if you use the data set option DBCREATE_TABLE_OPTS to create a primary index on a Teradata table for which the input data is from a different Teradata table. The problem occurs if the DBIDIRECTEXEC system option is set; not all of the processing is being done in the database but is instead being handled by SAS. SAS retrieves the data from the existing Teradata table and then, using SAS defaults for data types, issues the CREATE TABLE statement, including the primary index to Teradata. The data is then passed over to Teradata to be inserted into the newly created table. This process is slower because the data is being read in from and passed back to the Teradata table.

This process can also cause a data integrity issue. Some numerics and dates cannot be stored in SAS exactly as they were stored in Teradata. As a result, the new table does not contain exactly the same data as the existing data. There is also the potential that the data types for the new table might not be the same as those in the input table. This can occur because SAS, when building the CREATE TABLE statement, uses its default data types rather than the same data types for the columns that were defined in the original table. A data integrity issue might occur if the value is not stored in the same manner.

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to Teradata 9.21_M1 is available at:

A fix for this issue for Base SAS 9.21_M3 is available at:

A fix for this issue for SAS/ACCESS Interface to Oracle 9.21_M2 is available at:

A fix for this issue for SAS/ACCESS Interface to Teradata 9.21_M2 is available at: