Dropping Tables During a Load - Parallel Transporter

Teradata Parallel Transporter Application Programming Interface Programmer Guide

Product
Parallel Transporter
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-15
dita:mapPath
pev1488824663354.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2516
lifecycle
previous
Product Category
Teradata Tools and Utilities

Some tables are created by the Teradata Database during the execution of a job, and others must be created by the user before the job begins. When a job is run, the log table and error table are created automatically. The error table is dropped during the Cleanup phase if no errors were detected during the job. The log table is dropped after the job completes successfully.

If a job terminates abnormally, then the log and error tables are not dropped. If you want to restart the job from scratch, you need to manually drop these tables by running a BTEQ script to drop and recreate the tables.

Care must be taken dropping the target tables manually using a BTEQ script. If something goes wrong with a Stream job, and you drop the target table manually and then try to rerun the job, you may lose the original data.