Restarting a Job with Teradata Parallel Transporter - Access Module

Teradata® Tools and Utilities Access Module Reference

Product
Access Module
Release Number
16.20
Published
November 2020
Language
English (United States)
Last Update
2020-11-18
dita:mapPath
igy1527114222333.ditamap
dita:ditavalPath
igy1527114222333.ditaval
dita:id
B035-2425
lifecycle
previous
Product Category
Teradata Tools and Utilities

If a transfer terminates unexpectedly, you can restart the transfer. Under Teradata PT, the pipe writer process must restart from its beginning, but the Teradata PT infrastructure falls back to its last checkpoint, allowing the access module to synchronize the two. This saves time because the Teradata PT infrastructure does not have to reinsert into the destination table those records that have already passed through the pipe.

To specify a restart, issue the tbuild command with the -r option, as in the following example:

fexp < fexp.cmds > fexp.out & tbuild -r -f tbuild.txt &

In Teradata PT, the consumer operator cannot automatically direct the access module to restart, as do the client load utilities. All restarts require operator intervention.