Restrictions and Limitations - MultiLoad

Teradata® MultiLoad Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
MultiLoad
Release Number
20.00
Published
October 2023
Language
English (United States)
Last Update
2024-03-18
dita:mapPath
lji1691576359330.ditamap
dita:ditavalPath
kju1619195148891.ditaval
dita:id
sga1478609868891
Product Category
Teradata Tools and Utilities

The following table describes the Teradata MultiLoad restrictions and limitations on operational features and functions.

Feature Restrictions  
Operational Feature/Function Restriction/Limitation
Aggregate operators, exponential operators, arithmetic functions Not allowed
Concatenation of data files Not allowed
Concurrent load utility tasks The maximum number of concurrent Teradata MultiLoad tasks that can run is variable; the limit can be controlled by the system administrator. MaxLoadTasks may be overridden if TASM is active.
For the most up-to-date information on concurrent task limits, see the description of the MaxLoadTask parameter of the DBSControl utility in Teradata Vantage™ - Database Utilities, B035-1102. Additional information is available in the Teradata Dynamic Workload Manager User Guide (B035-2513).
If the Teradata MultiLoad job exceeds the recommended limits, the database returns a 2633 error message indicating that too many loads are running, and the utility retries until:
  • It can execute the task
  • It reaches the TENACITY hours time limit specified by the BEGIN MLOAD command
Data retrieval from the database with the SELECT statements Not allowed
Expressions Are evaluated from left to right, using the database order of preference, but can be overridden by parentheses.
Foreign key references Not allowed for a Teradata MultiLoad target table.

Attempting a Teradata MultiLoad task or any other action against a target table defined with a foreign key constraint produces an error condition.

Hash indexes Not supported
Hexadecimal form Teradata MultiLoad does not accept and will not display object names specified in internal Vantage hexadecimal form.
Join index restrictions Teradata MultiLoad does not support or maintain Join Indexes.
Journaling options There are no restrictions on journaling options. Teradata MultiLoad recognizes target tables with all types of currently supported journaling.
Maximum number of columns 2048
Maximum row size The maximum row size for a Teradata MultiLoad job, data plus indicators, is approximately 64,000 bytes. This limit is a function of:
  • The row size limit of the database
  • The Teradata MultiLoad work tables and error tables

Teradata MultiLoad cannot accommodate a row size that is near the row size limit of the database because of the operational overhead associated with Teradata MultiLoad work tables and error tables. If the Teradata MultiLoad job exceeds this limit, the database returns Error Message 3577 (row size or sort key size overflow), and terminates the job.

Maximum statement text length 1 MB
No primary index table Not allowed
Normalized Tables Not allowed
Unique secondary indexes Not allowed for a Teradata MultiLoad target table.

Target tables for a Teradata MultiLoad task may contain NUSIs, but not unique secondary indexes.

Tables with primary time index Not allowed.
Tables with referential integrity Not allowed.
Tables with defined triggers Not allowed.

PPI Table Considerations

Load utilities, including Teradata MultiLoad, are supported on PPI tables with the following restrictions and advisories:

  • Teradata MultiLoad does not support tables with Unique Secondary Indexes (USI). Many PPI tables have USIs.
  • Teradata MultiLoad IMPORT tasks require all values of the primary index column set and all values of the partitioning column set for deletes and updates.
  • Teradata MultiLoad IMPORT tasks do not support updates of the partitioning column set.
  • Teradata MultiLoad IMPORT tasks do not support primary index updates.
  • Teradata MultiLoad does not support hash and join indexes.

NoPI Table Considerations

A NoPI Table is a table that has no primary index. These tables can be used as staging tables where data is always appended to the table, making population of the table generally faster than that of a traditional table containing a primary index.

See the No Primary Index discussion in Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144.