move (Aster Database) | Commands | Teradata Data Mover - move (Aster Database) - Teradata Data Mover

Purpose

The move command creates a job to copy specified database objects from one database to another, then starts the job immediately. Use the command to create and start a job quickly without the XML object list by specifying tables on the command line. Data Mover supports moving tables between Teradata Database and Aster Database.

All parameters in this section are specific to the CLI.

Syntax

Parameters - Aster Specific

See Parameter Order.

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 86400 (24 hours) cause the job to fail at runtime.

source_aster_port | target_aster_port

[Optional] Source or target Aster Database server port.

source_aster_system_name | target_aster_system_name

Source or target Aster Database Queen node IP address or hostname.

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.

Parameters - Teradata to Aster

See Parameter Order.

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

See Parameter Order.

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.