Clean a Job | Teradata Data Mover - 17.11 - Cleaning Up a Job - Teradata Data Mover

Teradata® Data Mover User Guide

Teradata Data Mover
Release Number
Release Date
October 2021
Content Type
User Guide
Publication ID
English (United States)

Once a Data Mover job fails or is stopped with the stop command, the job might leave unwanted items on the source and target systems; including staging tables, error tables, and HUT locks. These remaining items can be removed with the cleanup command.

If the job used DSA, cleanup causes Data Mover to do the following:
  • Stop any remaining DSA tasks that are still running.
  • Release HUT locks from the source and target systems.

If the job used Teradata PT API or Teradata JDBC, cleanup causes Data Mover to drop error, work, log, and staging tables from the target system.

Use start to rerun the job from the beginning. The job cannot be restarted with restart after using the cleanup command.
Note the following considerations when cleaning up a job:
  • Data Mover drops the target table during cleanup only if the table was created as a result of a failed or stopped Data Mover Teradata PT API job. The drop occurs because the Teradata PT API job won't complete successfully the next time it is executed unless the target table has already been dropped.
  • With partial copies, Data Mover does not delete any rows that might have been inserted or updated in the target table.
  • If the Teradata PT API Stream operator was used, macros that the Stream operator created are not automatically cleaned up. Instead, clean up the macros manually.
  1. Type cleanup -job_name PayableJob1 on the command line.
    Where PayableJob1 is the job name displayed when the job was created.