Detecting and Correcting the Cause of Failure - Parallel Transporter

Teradata Parallel Transporter User Guide

Product
Parallel Transporter
Release Number
15.00
Language
English (United States)
Last Update
2018-09-27
dita:id
B035-2445
lifecycle
previous
Product Category
Teradata Tools and Utilities

Detecting and Correcting the Cause of Failure

Use the following procedure to detect and correct the errors that caused a job to fail:

1 Access the logs and error tables for the job.

For information on the content of the public and private logs and how to access them “Accessing and Using Job Logs” on page 155.

For information on the content of error tables and how to access them “Accessing and Using Error Tables” on page 160.

2 Evaluate the logs and any errors they contain.

  • If the job fails before attempting the first job step, the associated errors and warnings will be in the public log. Evaluate the log entries, and take the needed corrective action.
  • For a list of common errors for this type of failure, including causes and corrective actions “When the Job Fails to Begin Running” on page 174.

  • If the job runs but fails to complete, errors will be found in the public and private logs.
  • For a list of common errors for this type of failure, including causes and corrective actions “When the Job Fails to Complete” on page 181.

    3 If operator errors are detected in the private log, evaluate the corresponding information in the error tables to provide more detailed information on the errors.

    For detailed information on using error tables “Accessing and Using Error Tables” on page 160.

    4 Once the causes of errors have been corrected in the job script, re-launch the job.

    For information “Restarting A Job” on page 202.