Other Notes - Parallel Transporter
Teradata® Parallel Transporter Reference
- Product
- Parallel Transporter
- Release Number
- 17.10
- Published
- February 2022
- Language
- English (United States)
- Last Update
- 2023-11-29
- dita:mapPath
- abr1608578396711.ditamap
- dita:ditavalPath
- obe1474387269547.ditaval
- dita:id
- ogv1478610452101
- Product Category
- Teradata Tools and Utilities
- One SQL Inserter operator job can load a single database table or view.
- The target table must already exist.
- Data can be loaded into an empty or populated table.
- Only the Teradata SQL INSERT statement is supported. Any other Teradata SQL statements are not supported.
- One Teradata SQL INSERT statement is allowed for a single SQL Inserter operator job. Multiple statements are not allowed.
- One DML group is allowed for a single SQL Inserter operator job. Multiple DML groups are not allowed.
- The SQL Inserter operator treats the entire loading job as a single explicit transaction. If any error is encountered during the insert operation, the SQL Inserter operator backs out all rows of data inserted up to that point and the job terminates.
- The target table cannot be rolled back after the job is complete with no errors.
- Row hash level locking is used during the job. The job does not lock the target table.
- The SQL Inserter operator can support multiple instances, and each instance can log on one or more sessions based on the valued specified in the attribute MaxSessions.
- If multiple sessions are used and the data has duplicate primary index values, this could result in a potential database deadlock 2631 error. To avoid this error, do not use multiple sessions with the TPT SQL Inserter operator.
- If multiple sessions are used and the data accesses the same row-level lock on the database, the job could result in a hang. To avoid a hang, do not use multiple sessions with the TPT SQL Inserter operator. Use only one session.
- The SQL Inserter operator does not require a database load slot.