Teradata TPump uses conventional row hash locking, which allows for some amount of concurrent read and write access to its target tables. At any point, Teradata TPump can be stopped, making the target tables fully accessible. If Teradata TPump is stopped, however, depending on the nature of the update process, the relational integrity of the data may be compromised.
Although Teradata TPump always uses conventional row hash locking, based on the nature of SQL statements used in the Teradata TPump job and the status of the target tables, a Teradata TPump job may introduce other levels of locking in a job run. For example, if a target table of a Teradata TPump job has a trigger defined and this trigger uses table‑level locking when it is triggered, this Teradata TPump job may cause a table level‑locking if such a trigger is triggered during the run. The Teradata TPump script developer should be familiar with the property of the database on which the Teradata TPump job will run and be aware of such possibilities.