Problem Note 34696: Using the ERRLIMIT= option with the Teradata MultiLoad facility causes an access-violation error
The ERRLIMIT= option is not a supported option when you use the MultiLoad facilty. A number of errors occur at the end of each load phase.
In such a situation, the system attempts to ignore the fact that Teradata has run out of space, and it then attempts to send more records that it cannot process. As a result, an access violation that is similar to the following occurs:
ERROR: Read Access Violation In Task [ APPEND ]
Exception occurred at (3F39F37C)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
3F39F37C 0B55C5B0 sasiotra:\trmload.c\trchkne. 2824 +(0x4)
3F39D92C 0B55C8F4 sasiotra:\trmload.c\trmlins 1792 +(0xD)
3F39496D 0B55CB80 sasiotra:\trins.c\trins 210 +(0x5)
6335EF5E 0B55CBA4 sasxdbi:\dbiyoeu.c\yoeadd 451 +(0xA)
669433A0 0B55CDE4 sasyoio:\yosio1.c\yoadd 493 +(0xC)
667F3E0D 0B55D8AC sasqutil:\utz.c\zutapp 1765 +(0x3F)
667CB72C 0B55FC58 sasqutil:\util.c\utilrun 6708 +(0x16)
667C17B9 0B55FE5C sasqutil:\util.c\utrstmt2 1152 +(0xE)
667D8F2A 0B55FE70 sasqutil:\util.c\utrstmt 1042 +(0x7)
0286714A 0B55FEC0 sasxshel:\yspproc.c\yspproc 575 +(0x5)
66802CC6 0B55FEF0 sasqutil:\xsparse.c\xsparse 91 +(0x5)
667D9A11 0B55FF74 sasqutil:\util.c\utinit 807 +(0x5)
667C106D 0B55FF90 sasqutil:\util.c\sasqutil 660 +(0x5)
017E2854 0B55FFA4 sashost:\vvtentr.c\vvtentr 201
018CE038 0B55FFB8 sashost:htthread+0x38
77E64829 0B55FFEC kernel32:GetModuleHandleA+0xDF
To avoid this problem, do not use the ERRLIMIT= option in conjunction with the Teradata MultiLoad facility.
Operating System and Release Information
| SAS System | SAS/ACCESS Interface to Teradata | z/OS | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Microsoft® Windows® for x64 | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| HP-UX IPF | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| 64-bit Enabled Solaris | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| 64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| 64-bit Enabled AIX | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Windows Vista | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Linux | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
| Solaris for x64 | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
The ERRLIMIT= option is not available for MultiLoad because the number of errors are known only at the end of each load phase. The crash occurs because the system ignores the fact that Teradata has run out of space. Then the system tries to send more records (which it cannot handle).
| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Data Sources ==> External Databases ==> Teradata
|
| Date Modified: | 2011-06-06 12:33:40 |
| Date Created: | 2009-02-04 08:43:18 |
