Restrictions and Limitations | DDL Operator | Teradata Parallel Transporter - Restrictions and Limitations - Parallel Transporter

Teradata® Parallel Transporter Reference

Parallel Transporter
Release Number
February 2022
English (United States)
Last Update
Product Category
Teradata Tools and Utilities
This section describes the restrictions and limitations when using the DDL operator.
  • The DDL operator is neither a producer nor a consumer operator.

    The DDL operator is a standalone operator. The DDL operator cannot retrieve data records from the Teradata PT data stream and send them to the database. The DDL operator cannot export rows from the database.

  • The DDL operator uses one session; it does not support multiple sessions.
  • The DDL operator uses one instance; it does not support multiple instances.
  • By default, if the DDL operator encounters an error, the DDL operator treats the error as a fatal error and terminates the job. You can override this behavior by using the DDL operator's ErrorList attribute.
  • The DDL operator supports every SQL statement, except statements that return data to the operator, such as the SELECT, HELP, and SHOW statements. There are two exceptions:
    • The CREATE REPLICATION GROUP statement is supported. The user needs the group id and/or the token after a replication group is created.
    • The INSERT...SELECT statement is supported; it returns the total number of rows being inserted in the table.
  • A USING clause cannot be specified with any SQL statements that send data to the database.
  • All data values used by the SQL statements must be hard-coded into the SQL statements.
  • The DDL operator restarts at the beginning of the group of SQL statements whose execution is interrupted by an abnormal termination.
  • The DDL operator can send SQL statements up to 1MB to the database.
  • The DDL operator does not require a database load slot.