• Print |
• E-mail  |
• Bookmark

The following error message(s) may be issued when you attempt to
FastLoad using SAS/ACCESS Interface to Teradata:

Bus Error In Task ( SQL      ]
  Fault Occurred at
[/usr/local/add-on/sas82/sasexe/sasiotra:trfasbuf+0x70]

  Task Traceback

  /usr/local/add-on/sas82/sasexe/sasiotra:trfasbuf+0x70
  /usr/local/add-on/sas82/sasexe/sasxdbi:yoeaddl+0x50

---or---

Segmentation Violation In Task ( DATASTEP ]
  Fault Occurred at [/802p0/usrlibsas/sasexe/sasiotra:trfasbuf+0x310]

  Task Traceback

  /802p0/usrlibsas/sasexe/sasiotra:trfasbuf+0x310
  /802p0/usrlibsas/sasexe/sasxdbi:yoeaddl+0x50

If you receive these errors, you may be experiencing a known
SAS/ACCESS Interface to TERADATA bug.

On certain SUN/Solaris hardware, the bus error can crash SAS.  None of
the hardware SAS has in-house exhibits this problem.  However, on a
simple FastLoad, customers have experienced the above-mentioned bus
error that crashes SAS.

Below is a version of the user's SAS test program, which demonstrates
this problem.

  /*** This produced the BUS ERROR above ***/
  libname templib teradata user=XXXXXXX password=XXXXXXXXXXXXXXXX
  tdpid=pzdb  schema=WCDBUSERTEMP;
  libname tdblib teradata user=XXXXXXX password=XXXXXXXXXXXXXXXX
  tdpid=pzdb  schema=WCDBCOREVM;
  libname ivr '/thor/CPA/ivr/ivr0716';
  6    /* create a list of TNs */
  7    data ivr.tn;
  8    set ivr.detail;
  9    length TN $ 10;
  10   keep TN;
  11   TN = incoming_ani;

  NOTE: There were 300472 observations read from the data set
IVR.DETAIL.
  12   proc sort data=ivr.tn;
  13   by TN;
  14   data ivr.tn;
  15   set ivr.tn ;
  16   by TN;
  17   if first.TN;
  19   proc sql;
  20   drop table templib.DIS00501_WORK;
  21   create table templib.DIS00501_WORK(fastload=yes) as select *
  from ivr.tn;

The segmentation violation error was discovered internally at SAS and
occurs on all platforms on which SAS/ACCESS Interface to Teradata is
available.  If you FastLoad to a Teradata table using data read
from another Teradata table, SAS will crash.  This occurs only when a
lot of data is read and FastLoaded.  The problem: the Teradata DBMS
returns as a viable connection the one that is being used by the read.
The result a segmentation violation.

Here is the code that demonstrates the this problem.

  /*** This produced the segmentation violation error above ***/
  libname a teradata user=dbitest password=dbigrp1;
  libname b teradata user=sasdxs password=sasdxs1;
  proc delete data=b.defects121127; run;
  data b.defects121127(fastload=yes sessions=2);
  set a.defects121127; run;

A Technical Support hot fix for Release 8.2 TSLEVEL TS2M0 for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#005626

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at: