Configuring Teradata Data Mover

After deploying a Data Mover VM, 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 VM defaults to the database time zone.

The steps in this procedure apply to all deployment methods except where noted.

  1. From the Azure portal, note the following of the Data Mover VM:
    • The private IP address.
    • If applicable, either the public IP or public DNS.
  2. Log on to the VM using the authentication type you chose when deploying the VM.
  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 VMs including each additional Data Mover agent VM
    • DNS
    The TDPIDs can be used in the Data Mover job XML for data movement.
  6. Run the following commands to verify Data Mover components are ready to use.
    # datamove list_jobs
    # datamove list_agents
  7. Do one of the following to move data:
    • Deploy a Viewpoint VM 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 VM ID.

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

    • Use the Data Mover command-line interface.
    • Use the Teradata REST Services interface.
For information about how to use these interfaces, see the Teradata Data Mover User Guide.
Additional configuration is required for the DSA components that are bundled with Data Mover. Refer to the instructions in DSA Setup for New Teradata Systems in the Teradata Data Mover Installation, Configuration, and Upgrade Guide for Customers.
When stopping and starting instances, the Data Mover instance must be started before the source and target Teradata systems so that DSMain on the Teradata servers can properly register with the Data Mover ActiveMQ instance. If the Data Mover instance was not started first, then DSMain must be restarted on the Teradata servers before using Data Mover with DSA. To restart DSMain first stop it by running "start dsmain -s" followed by "start dsmain" in a cnsterm session on the Teradata server.

results matching ""

    No results matching ""