17.00 - Dropping Tables During a Load - Parallel Transporter

Teradata® Parallel Transporter Application Programming Interface Programmer Guide

prodname
Parallel Transporter
vrm_release
17.00
created_date
June 2020
category
Programming Reference
featnum
B035-2516-220K

Some tables are created during the execution of a job, but others must be created by you before the job begins. Target tables must exist on the database when an Update driver job is executed. The log table is created automatically when you run the Update job script. Error tables and work tables are created by the database. Error tables are dropped by the Update driver during the cleanup phase if no errors were detected during the acquisition phase or the application phase. The work table is dropped by the Update driver during the cleanup phase if no errors were detected during the acquisition or the application phase. The log table is dropped by the Update driver after the job completes successfully.

When a job terminates abnormally, the log, error, and work tables may not be dropped depending on where in the job the termination occurred. If you want to restart the job from the beginning, you need to manually drop these tables by running a BTEQ script.

Care must be taken when you manually drop the target tables using a BTEQ script. If something goes wrong with an Update job and you drop the target tables manually, when you try to rerun the job, you may lose the original data. Because all rows are held in work tables until the Update job reaches the application phase (when they are copied to the target tables), you risk losing the original data.