Usage Note 40400: EM_DBC_CRASH_A(220) errors when using SAS/ACCESS® Interface to Teradata
 |  |  |  |
When extracting large volumes of data from Teradata databases using SAS/ACCESS Interface to Teradata, the following error can occur:
ERROR: Teradata row not delivered (trget): MTDP: EM_DBC_CRASH_A(220):
Network connection to the DBC was lost.
Network connection to the DBC was lost.
The problem occurs because the network connection has timed out due to the fact that the Teradata server is either too busy or the network is overwhelmed by the query.
To circumvent the problem, use more efficient Teradata connections such as using the FastExport utility or TPT Fastexport to extract the data.
Examples using FastExport are shown below:
libname trlib teradata user=username password=userpwd fastexport=yes;
proc print data=trlib.employees;
where lastname=’lovell’;
run;
proc print data=trlib.employees;
where lastname=’lovell’;
run;
/* Use explicit Pass-Through SQL with PROC SQL & supply the
SQL yourself, also starting FastExport. */
proc sql;
connect to teradata(user=username password=userpwd fastexport=yes);
select * from connection to teradata
(select * from sales where gender=’f’ and salesamt>1000);
quit;
SQL yourself, also starting FastExport. */
proc sql;
connect to teradata(user=username password=userpwd fastexport=yes);
select * from connection to teradata
(select * from sales where gender=’f’ and salesamt>1000);
quit;
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Teradata | Windows 7 Professional 32 bit | 9.2 TS2M3 | |
| Windows 7 Home Premium x64 | 9.2 TS2M3 | |||
| Windows 7 Home Premium 32 bit | 9.2 TS2M3 | |||
| Windows 7 Enterprise x64 | 9.2 TS2M3 | |||
| Windows 7 Enterprise 32 bit | 9.2 TS2M3 | |||
| Microsoft Windows XP Professional | 9.2 TS2M3 | |||
| Microsoft Windows Server 2008 for x64 | 9.2 TS2M3 | |||
| Microsoft Windows Server 2008 R2 | 9.2 TS2M3 | |||
| Microsoft Windows Server 2008 | 9.2 TS2M3 | |||
| Microsoft Windows Server 2003 for x64 | 9.2 TS2M3 | |||
| Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M3 | |||
| Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M3 | |||
| Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M3 | |||
| Microsoft® Windows® for x64 | 9.2 TS2M3 | |||
| z/OS 64-bit | 9.2 TS2M3 | |||
| z/OS | 9.2 TS2M3 | |||
| Windows 7 Professional x64 | 9.2 TS2M3 | |||
| Windows 7 Ultimate 32 bit | 9.2 TS2M3 | |||
| Windows 7 Ultimate x64 | 9.2 TS2M3 | |||
| Windows Vista | 9.2 TS2M3 | |||
| Windows Vista for x64 | 9.2 TS2M3 | |||
| 64-bit Enabled AIX | 9.2 TS2M3 | |||
| 64-bit Enabled HP-UX | 9.2 TS2M3 | |||
| 64-bit Enabled Solaris | 9.2 TS2M3 | |||
| HP-UX IPF | 9.2 TS2M3 | |||
| Linux | 9.2 TS2M3 | |||
| Linux for x64 | 9.2 TS2M3 | |||
| Solaris for x64 | 9.2 TS2M3 | |||
Errors can occur when extracting large volumes of data or when a Teradata server is very busy. This indicates that the network is timing out and cannot complete the query.
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2010-12-20 15:46:27 |
| Date Created: | 2010-07-21 12:55:54 |