![]() | ![]() | ![]() | ![]() | ![]() |
FastLoad sessions that are allocated by SAS/ACCESS® Interface to Teradata can cause a job to terminate. The problem occurs when you use the Teradata FastLoad utility with the SLEEP=, TENACITY=, and BULKLOAD=YES options.
The problem occurs when the number of server utility slots has been exceeded and a FastLoad job is submitted with the TENACITY= and SLEEP= options are tenacity and sleep set.
When the application tries the FastLoad connection, the connection failure is not automatically canceled or deallocated in CLI. Because the connection failure is not deallocated, the orphaned session is still active in the FastLoad session pool when the FastLoad job succeeds in gaining a utility slot to run. If FastLoad calls new sessions, these sessions can conflict with the existing failed connection. As a result, the entire job then fails.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | SAS Release | |
Reported | Fixed* | |||
SAS System | SAS/ACCESS Interface to Teradata | z/OS | 9.2 TS2M0 | |
Microsoft® Windows® for x64 | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 for x64 | 9.2 TS2M0 | |||
Microsoft Windows Server 2008 for x64 | 9.2 TS2M0 | |||
Microsoft Windows XP Professional | 9.2 TS2M0 | |||
Windows Vista | 9.2 TS2M0 | |||
Windows Vista for x64 | 9.2 TS2M0 | |||
64-bit Enabled AIX | 9.2 TS2M0 | |||
64-bit Enabled HP-UX | 9.2 TS2M0 | |||
64-bit Enabled Solaris | 9.2 TS2M0 | |||
HP-UX IPF | 9.2 TS2M0 | |||
Linux | 9.2 TS2M0 | |||
Linux for x64 | 9.2 TS2M0 | |||
Solaris for x64 | 9.2 TS2M0 |