Running multiple, concurrent processes causes an error in the FastLoad utility when you use it with the SAS/ACCESS Interface to Teradata. To create unique names for the FastLoad error logs, the application appends the number of seconds since midnight, January 1, 1960 to the prefix SAS_FASTLOAD_ERRS1 and SAS_FASTLOAD_ERRS2. When you run multiple instances of FastLoad by different processes concurrently, just appending the number of seconds since January 1, 1960 is not sufficient to create unique table names.

The solution involves using the first 15 characters from the table name, then appending _SE1_ or _SE2_ (for sites that use logic to clean up error files that are created by failed FastLoad jobs), and then appending a 10-digit number that represents the number of seconds after 1960.

Example:

For a table named Fast56789012345678901 and with a number of seconds that equals 1234567890, the error logs will be named Fast56789012345_SE1_1234567890 and Fast56789012345_SE2_1234567890.

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: