With Teradata Parallel Transporter
If a transfer terminates unexpectedly, you can restart the transfer. Under Teradata Parallel Transporter, the pipe writer process must restart from its beginning, but the Teradata Parallel Transporter infrastructure falls back to its last checkpoint, allowing the access module to synchronize the two. This saves time because the Teradata Parallel Transporter 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 Parallel Transporter, the consumer operator cannot automatically direct the access module to restart, as do the client load utilities. All restarts require operator intervention.