Normalized Tables
The Load operator does not support normalized tables.
A normalized table is a table that has been created using the NORMALIZE clause in
the CREATE TABLE statement. To normalize means to combine two period values that meet
or overlap.
Restrictions and Limitations
This section describes the restrictions and limitations when using the Load operator.
Table Characteristics and Considerations
The target table cannot have any of the following characteristics:
Join, hash, or secondary indexes
Foreign key references
Referential integrity
Triggers
Cannot be a normalized table
Cannot be a column partitioned table
Data Types
The job cannot export these data types:
LOB
JSON
XML
ST_Geometry
UDT data can be loaded in its external type format.
Error Tables
Error tables cannot exist for new jobs.
The table names for the ErrorTable1 and ErrorTable2 attributes must be new tables
unless you are restarting a paused Load operator job.
Other Notes
One Load operator job can load a single Teradata table.
The target table must already exist and be empty for new jobs. The empty table restriction
applies to PI and NoPI tables.
The target table is locked until the application phase is complete.
The target table cannot be rolled back after the application phase is complete.
Duplicate rows are discarded by the Teradata Database for SET and MULTISET tables.
The exception is NoPI tables. Duplicate rows are not discarded for NoPI tables.
Only the Teradata SQL INSERT statement is supported. Any other Teradata SQL statements
are not supported.
The job cannot load data into a view.
The Load operator requires one Teradata Database load slot.