Configuring Data Mover - Teradata Software for AWS

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

Product
Teradata Vantage on AWS
Release Number
5.08
Published
November 2018
Language
English (United States)
Last Update
2018-11-07
dita:mapPath
upc1519757374969.ditamap
dita:ditavalPath
TeradataAWS_PubCloud_5.08.ditaval
dita:id
B035-2800
lifecycle
previous
Product Category
Cloud
Although you can configure this software yourself, we recommend contacting Teradata instead. See https://www.teradata.com/Consulting/Velocity.

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 Teradata Database 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 Web 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.
    # pdestate -a
    PDE state is RUN/STARTED. DBS state is 4: Logons are enabled - Users are logged on The Data Mover components automatically start after the Teradata Database 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 changepassword.sh script is located in the /var/opt/teradata/packages/DataMover directory.
    Option Description
    Interactively
    1. Run changepassword.sh without arguments.
      # changepassword.sh
    2. Enter responses to the prompts to complete the process.
    Non-interactively
    1. Run changepassword.sh with the -o, -p, -m, and -d arguments.
      # changepassword.sh 
      -o  existing-dbc-password 
      -p  new-dbc-password
      -m  existing-datamover-password
      -d  new-datamover-password

      Automated scripts change the password based on your input.

  7. [After Manual or 1-Click Launch only] Restart the Data Mover daemon.
    # /etc/init.d/dmdaemon stop
    # /etc/init.d/dmdaemon start

    Additional configuration is required for the bundled DSA components. Refer to the instructions in DSA Setup for New Teradata Systems in the Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers.

  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 the Teradata® Data Mover User Guide.