Job Overview | Teradata Data Mover - Data Mover Jobs - Teradata Data Mover

Teradata® Data Mover User Guide - 20.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
hlv1700545853003.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
don1467241476387
Product Category
Analytical Ecosystem
A Data Mover job consists of the following:
  • A user-provided definition of database objects that Data Mover copies from the source to the target, such as a copy of a table from the PROD1 Vantage system to the DEV1 Vantage system.
  • A programmatically-generated plan of sequential and parallel tasks to optimize job execution, such as distributing job execution into tasks across several servers.
A job is useful for the following tasks:
  • Copying database objects.
  • Copying one or more tables from an existing Vantage system to a backup Vantage system, where data in both systems stays synchronized.
  • Copying data from a production Vantage system to a staging or test Vantage system.
  • Migrating data regularly in one direction from the original to a backup.
When creating a job, you select source and target databases and specify the source database objects to copy. You can also refine the job definition to control performance, logging, and other factors.
Spaces in the user or account name for the source or target ID cause jobs to fail.
The jobs continue to exist after being run, including job definition and history, whether successful or not. You can delete these jobs if they are no longer needed.
Only one instance of a specific job can run at one time.

Data Mover jobs that are created with the command-line or RESTful API move command act the same as running the create command followed by the start command.