About Job Settings - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
rdo1467305237457.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
Jobs have default settings that are applied after a job is created. You can make changes to the default job settings using the Job Settings tab.
Field Description
Priority Set the relative priority for executing a job. Data Mover uses this priority to determine which jobs should be executed first when multiple jobs are in the execution queue. This priority is also used to determine which tasks are executed first. The options are Low, Medium, and High. The default is Medium. Jobs designated as high priority are started before lower priority jobs when they are queued to run. A column indicating job priority is available for display in the Saved Jobs view.
Use online archive Set read and write access to a source table while the table is copied to the target. Applies only to Teradata ARC jobs. You can update the source table during the copy process, but the changes are not transferred to the target table. Instead, the data contained in the target table matches the data that was in the source table at the beginning of the copy process.

Online archiving demands more processing so expect job performance to be reduced.

Logging level Set the amount of detail provided for job logging as follows:
  • Off: Disable logging.
  • 1: Enable minimal logging. Provides essential information, such as error and warning messages.
  • 2: Enable more logging. Provides additional information, including informational messages for example.
  • 99: Enable full logging. Provides detailed information, including debug messages for example.
Allow overwrite Set to overwrite tables and objects on the target automatically, if the target table or object exists.
The following describes the behavior when moving join indexes, hash indexes, journals, and triggers to Teradata Database:
Same Name Join or Hash Index
If the join or hash index of the source database is named the same as that in the target database, it is overwritten.
Table with associated Join or Hash Index
Moving a table that exists on the target with an associated join or hash index overwrites the target table and recreates the join or hash index on the newly copied table.
Table with a Permanent Journal
The target table must use the same journal name as the source table. An error results if journal source and target names are different.
Trigger Exists with Same Name
If a trigger exists on the target database with the same name as in the source and within the same database, it is overwritten.
Table Exists with Trigger
If a table exists on the target with a trigger, the target table is overwritten. The trigger is recreated on the newly copied table.
Compare DDL Set to compare the DDL of source tables and views with those of their existing target tables and views. Views are compared only if their copyData attributes have been specified as true.
  • Default: Use the option set for the daemon in the Data Mover Setup portlet.
  • True: Compare the DDL of source tables and views to those of their corresponding target tables and views.
  • False: Do not compare the DDL of source tables and views to those of their corresponding target tables and views.
Event table logging Set logging of events related to the job by clicking the Edit button and selecting one or more event tables.

The options are displayed if event tables are specified in the Data Mover Setup portlet.

Job Permissions Set the read, write, and execute permission for users and roles.
Use User ID pool Set to make multiple users in a target system available for running a job. Applies only to Teradata ARC jobs. Before using this option in a job, the Teradata Viewpoint Administrator must first add user names and passwords for the target system in Data Mover Setup.
Freeze job steps Set to verify any changes in the source and target environments between the time the job was first created and the time it is run. If you select this option you can later update job steps from the Saved Jobs view.
This option generally improves performance.
File Options For Hadoop, select Text, RC, or ORC and any delimiters, such as comma (,).
Foreign Server Name Select the foreign server that was created to copy data between either Teradata and Teradata systems or Teradata and Hadoop systems.
Query Band Set to tag sessions or transactions with user-defined name-value pairs. If you define a query band for a job, Data Mover uses that definition for all transactions on the source and target systems for the job.
Target Database Set a default target database that is used for all database objects included in the job request. Click to select a database. You can use the filter to display only the items that match the characters you enter.
Staging Database for Tables Set a default staging database for tables that is used for all tables included in the job request. Click to select a database. You can use the filter to display only the items that match the characters you enter.
Staging Database for Temporary Artifacts Set a default staging database for temporary artifacts, such as work tables, log tables, error tables, or macros. Click to select a database. You can use the filter to display only the items that match the characters you enter.