Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

The Teradata FastLoad utility may fail due to space constraints caused
by using a poor primary index.

When FastLoad is used from SAS, SAS will formulate a CREATE TABLE,
and will not explicity assert a Teradata primary index for the table.
In this case the first column of the table will be asserted as the
primary index.  If the column happens to be a bad choice for the primary
index, the data distribution across the AMPs (nodes) will be skewed.
This could cause some AMPs to receive many rows while others only
receive a few.  Bad skewing could cause one of the AMPs to run out of
space.

To circumvent this situation, explicitly assert the primary index in the
SAS code.  For example:

   data tra.mg_churn_BAMCR_aug_sep01_v2(fastload=yes sessions=4
   dbcreate_table_opts = 'primary index(cust_id,cust_line_seq_id)');

If the above is not the problem, then the problem may be simply not
having enough PERMSPACE available for a particular database/user.

To determine the total amount of space available for a particular
database/user, divide PERMSPACE by the number of AMPs.

Note: PERMSPACE is defined under Teradata.  For more information
      on this, please contact NCR.

Operating System and Release Information