Configuring Teradata Data Mover

Depending on how you launched your instance, use the following table to determine whether you need to complete this procedure.
Ecosystem CloudFormation Manual 1-Click
No No Yes Yes

After launching a Data Mover instance, you must check the Teradata Database status, verify Data Mover components are ready to use, and then Data Mover is ready to use.

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.
    For information, see Connection Considerations.
  2. Do one of the following from the SSH client console:
    Launch Type Action
    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 ec2-user@public-IP or public-DNS
    where:
    • The private-key-file is the private key file (.pem) of the AWS key pair specified when launching the instance.
    • The public-DNS or public-IP is the DNS host name or public IP address of the Data Mover instance.
  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 up after the Teradata Database repository has started.
  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 instances
    • DNS
    The TDPIDs can be used in the Data Mover job XML for data movement.
  6. [Only for Manual and 1-Click] 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 launch of the instance is dbc. The default DATAMOVER password upon initial launch 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  old dbc password  
      -p  new dbc password  
      -m  old datamover password  
      -d  new datamover password
      where:
      • old dbc password is the existing password for the DBC user.
      • new dbc password is the new password for the DBC user.
      • old datamover password is the existing password for the DATAMOVER user.
      • new datamover password is the new password for the DATAMOVER user.

      Automated scripts change the password based on your input.

  7. [Only for Manual and 1-Click] Restart the Data Mover daemon.
    # /etc/init.d/dmdaemon stop
    # /etc/init.d/dmdaemon start
  8. [Only for Manual and 1-Click] Run the following commands to verify Data Mover components are ready to use.
    # datamove list_jobs
    # datamove list_agents
  9. Do one of the following to move data:
    • Launch a Viewpoint instance to use the Data Mover portlets by logging on to the Viewpoint portal with the user name of admin and enter the same password as the Viewpoint instance ID.

      The Data Mover portlets are pre-installed on the Viewpoint instance.

    • Use the Data Mover Command-Line Interface.
    • Use the Teradata REST Services interface.
For information on how to use these interfaces, see the Teradata Data Mover User Guide.

results matching ""

    No results matching ""