edit (Aster Database) - 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

Purpose

The edit command modifies an existing job definition. All previous job executions will be linked with the new job definition.

All parameters in this section are specific to the CLI.

Parameters - Aster Specific

These parameters are specific to Aster Database when using the CLI to edit a job definition for moving tables from Aster to Teradata or Teradata to Aster.
source_aster_system_name | target_aster_system_name
Source or target Aster Database Queen node IP address or hostname.
source_aster_port | target_aster_port
[Optional] Source or target Aster Database server port.
source_aster_user_name | target_aster_user_name
Source or target Aster Database user name.
source_aster_user_password | target_aster_user_password
[Optional] Source or target Aster Database password.
source_aster_user_password_encrypted | target_aster_user_password_encrypted
[Optional] Source or target Aster Database encrypted password. Not a valid parameter if source_aster_user_password | target_aster_user_password is specified.
aster_query_timeout
[Optional] Specifies the response time allowed in seconds. If not supplied, the default timeout is 30 minutes. Data Mover allows all non-negative values; however, values greater than 3600 will cause the job to fail at runtime.

Parameters - Teradata to Aster

This parameter is specific to Aster Database when using the CLI to edit a job definition for moving tables from Teradata to Aster.
aster_preserve_column_case
[Optional] Specifies case for column names. Values:
  • No: Default. Changes all table names to lowercase.
  • Yes: Keeps the existing case for column names when transferring to Aster Database.

Parameters - Aster to Teradata

This parameter is specific to Aster Database when using the CLI to edit a job definition for moving tables from Aster to Teradata.
aster_skip_error_records
[Optional] Specifies treatment of errors encountered when loading data to Aster Database. When using load_from_teradata, the connector can encounter an error parsing a row containing data that is valid in Teradata but is not supported in Aster Database.
  • No: Default. Load is aborted upon encountering an error, and no rows are loaded to Aster Database.
  • Yes: Keeps the existing case for column names when transferring to Aster Database.