Configure Data Mover | Teradata Vantage on AWS (DIY) - 2.2 - Configuring Data Mover - Teradata Vantage on AWS

Teradata Vantage™ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
2.2
Release Date
May 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-2800-041K
Language
English (United States)
Although you can configure this software yourself, we recommend contacting Teradata Ecosystem Services. See https://www.teradata.com/About-Us/Contact.

Depending on how you launched your instance, use the following table to determine whether you need to complete this procedure.

Ecosystem AWS CloudFormation Manual 1-Click
Yes Yes Yes Yes

After deploying a Data Mover instance, you must check the Vantage status, verify Data Mover components are ready to use, and install and configure the ClientHandler package on source and destination Teradata systems.

The time zone for the Teradata Data Mover instance defaults to the time zone of the AWS availability zone.

  1. From the AWS Management Console, note the Private IP and either the Public IP or Public DNS of the Data Mover instance.
  2. Do one of the following from the SSH client console:
    Deployment Type Action
    Ecosystem and AWS CloudFormation Log on to the Data Mover master instance as ec2-user using the applicable AWS key pair.
    Manual and 1-Click Log on to the Data Mover instance as ec2-user using the applicable AWS key pair.
    # ssh -i  private-key-file.pem  ec2-user@data-mover-public-IP  data-mover-public-DNS
  3. Switch to the root user environment.
    # sudo su -
  4. Check the status of the database.
    # service postgresql status
    PDE state is RUN/STARTED.
    DBS state is 4: Logons are enabled - Users are logged on
    The Data Mover components automatically start after the Vantage repository starts.
  5. If Teradata is used as a source and target system for data movement, add the COP entries with private IP addresses to one of the following:
    • /etc/hosts file on all Data Mover instances including each additional Data Mover agent instance
    • DNS
    The TDPIDs can be used in the Data Mover job XML for data movement.
  6. [After Manual or 1-Click Launch only] Change the default DBC account password and DATAMOVER password for the internal Data Mover repository, either interactively or non-interactively.
    The default DBC password upon initial deployment of the instance is dbc. The default DATAMOVER password upon initial deployment of the instance is datamover.
    The change_pg_password.sh script is located in the /var/opt/teradata/packages/DataMover directory.
    The following special characters are not allowed in passwords: Single quote ('), double quotes ("), and blank spaces ( ).

    Perform either of the following:

    Option Description
    Interactively
    1. Run change_pg_password.sh without arguments.
      # changepassword.sh
    2. Enter responses to the prompts to complete the process.
    Non-interactively
    1. Run change_pg_password.sh with the -o, -p, -m, and -d arguments.For example:
         change_pg_password.sh
       -o <Current password for user 'postgres'>
       -p <New password for user 'postgres'>
       -m <Current password for user 'datamover' & 'bar'> 
      -d <New password for user 'datamover' & 'bar'>
       
      
      NOTE: DATAMOVER & BAR user passwords have to be the same# 
  7. [After Manual or 1-Click Launch only] Restart the Data Mover daemon.
    # /etc/init.d/dmdaemon stop
    # /etc/init.d/dmdaemon start
  8. [After Manual or 1-Click Launch only] Run the following commands to verify Data Mover components are ready to use.
    # datamove list_jobs
    # datamove list_agents
See Teradata® Data Mover User Guide, B035-4101.
PostrequisiteAdditional configuration is required for the bundled DSA components. See "DSA Setup for New Teradata Systems" in Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers , B035-4102 .