15.00 - Restrictions and Limitations - FastLoad

Teradata FastLoad Reference

prodname
FastLoad
vrm_release
15.00
category
Programming Reference
featnum
B035-2411-034K

Restrictions and Limitations

The following sections describe restrictions and limitations relevant for programming with the Teradata FastLoad utility.

Session Limits

The value specified with the SESSIONS command is not the only factor that limits the number of sessions that Teradata FastLoad establishes with the Teradata Database. The other limiting factors are:

  • The Teradata Database limit of one session per AMP.
  • The platform limit on the maximum number of sessions per application.
  • This value is defined in the Communications Processor (COP) Interface software file, CLISPB.DAT, under the MaxSess variable.

    The TDP SET MAXSESSIONS command can be used to specify a platform limit. The default limit is equal to the server MAXSESS.

  • The limit of the network protocol software on network‑attached systems.
  • When invoking Teradata FastLoad, the actual session limit is determined by whichever limiting factor is encountered first.

    Space Requirements and Limitations

    Always estimate the final size of the Teradata FastLoad table, and make sure that the destination database on the Teradata Database has enough space to accommodate the Teradata FastLoad job. If the database that owns the Teradata FastLoad table or the error tables runs out of space, the Teradata Database returns an error message and Teradata FastLoad pauses your Teradata FastLoad job. When this happens, allocate more space to the database before restarting the job.

    Join Index Restrictions

    Teradata FastLoad does not maintain join indexes. Teradata FastLoad cannot be used to load data to tables with an associated join index on a Teradata Database. In this case, first drop the join index, then recreate it after running the Teradata FastLoad job.

    Note: Teradata FastLoad does not support hash and join indexes.

    Foreign Key References Limitation

    Teradata FastLoad does not support foreign key references in target tables. Attempting a Teradata FastLoad task or any action against a target table defined with a foreign key constraint produces an error condition.

    Secondary Indexes Limitation

    Teradata FastLoad does not support target tables defined with secondary indexes. Attempting a Teradata FastLoad task against a target table defined with secondary indexes produces an error condition.

    To load such a table, first drop the secondary indexes. Then load the table and recreate the secondary indexes.

    Or, alternatively, if only nonunique secondary indexes (NUSI) are involved, consider using MultiLoad.

    Note: Teradata FastLoad does not support secondary indexes of any kind.

    Referential Integrity Limitation

    Attempting a Teradata FastLoad task or any action against tables with [referential integrity|defined triggers] produces an error condition.

    Defined Triggers Limitation

    Attempting a Teradata FastLoad task or any action against tables with [referential integrity|defined triggers] produces an error condition.

    Normalized Table Restrictions

    Teradata FastLoad is not allowed on a normalized PI table when PI column is part of the ignore column list.

    Teradata FastLoad is not allowed on a normalized NoPI table.