Restarting a Job "Catch Up"|TPT - Restarting a Job "Catch Up" - Parallel Transporter

Teradata® Parallel Transporter User Guide - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Parallel Transporter
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-08-25
dita:mapPath
uzp1645128359760.ditamap
dita:ditavalPath
tvt1507315030722.ditaval
dita:id
B035-2445
Product Category
Teradata Tools and Utilities

Here are the steps for switching the load protocol to perform “catch up”:

  1. Terminate the current job with the TERMINATE command. This forces the job to take a checkpoint before it terminates.
  2. Switch the load protocol by either changing the operator in the job variables file or by using another job variables file that has the new operator. The latter method is highly recommended because it prevents users from modifying existing job variables files.
  3. Resubmit the same job with the same command options.
    Do not cleanup the Teradata PT checkpoint files left from the previous run.

    These steps can be easily automated because performing "catch up" is very similar to restarting a job. In most of the "catch up" cases, you do not need to modify the original scripts. This is all due to the advantages of having a single script language, external job variables to isolate changes to one place, and a common protocol for checkpoint restart across operators.