6.02 - Upgrading Data Mover - Teradata Software for Azure

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

Teradata Vantage on Azure
Release Number
Release Date
January 2019
Content Type
Publication ID
English (United States)
Open a maintenance window to see the status of the Teradata software during the upgrade process, including data, reports, and summary alerts.
After initiation, the upgrade process is completely non-interactive. During the upgrade, PUT reboots the system.

When performing a major upgrade, you must redeploy the system.

  1. Download the required upgrade bundles.
  2. Log in as the root user to the system where the component you are upgrading is installed.
  3. If the following directory does not exist, create it: /var/opt/teradata/swupgrade-source
  4. Transfer the downloaded upgrade bundles to /var/opt/teradata/swupgrade-source.
  5. Create a dsainputs file. For Teradata Data Mover 16.20 and later, DSC is installed and upgraded with Data Mover.
    1. Copy the tdm-linux-upgrade__sles11sp3_x8664.XXXXX-1.tar.gz to /var/opt/teradata/swupgrade-source.
    2. Untar the following:
      # tar xzvf tdm-linux-upgrade__sles11sp3_x8664.XXXXXXX-1.tar.gz
      # tar xzvf tdm-linux__linux_indep.XXXXX-1.tar.gz
    3. Type ./build_dsainputs -d to create the /tmp/dsainputs file.
    4. Verify there is at least 100 GB in the Data Mover repository on the Data Mover master node to dedicate to DSC.
    5. If there is not enough space in the Data Mover repository, update the BARSIZE property in the tmp/dsainputs file to less than 100 GB.
    6. In the Data Mover master node where DSC is installed, type the following and press Enter to obtain output.
      # ifconfig eth0 | grep inet | grep -iv inet6 | awk '{print $2}' | sed -ne 's/addr\://p'
    7. Using the output, update the DSCNAME property in the /tmp/dsainputs file, using 22 alphanumeric characters or less.
  6. Change to the PUT bin directory: /opt/teradata/TDput/bin
  7. For a single-node Data Mover system or a master node in a multi-node system, do the following:
    1. Run the swupgrade -U command:
      • If the TDput version is or higher, set an environmental variable with your dbc password and run the swupgrade with the -d option:
        # export SWUPGRADEDBC='xxx'
        # /opt/teradata/TDput/bin/swupgrade -U -d
        where xxx is your dbc password. If the password contains any special characters, you must use single quotes around your dbc password.
      • If the TDput version is lower than, change the dbc password from the repository to dbc and run the command:
        # /opt/teradata/TDput/bin/swupgrade -U

        We recommend changing the dbc password back to the original password once the upgrade is successful.

      Progress messages display on the screen until the system reboots.
    2. Log on to the system and run this command to display the log as the upgrade completes: tail -f /var/opt/teradata/TDput/fileservice/logs/swupgrade.log PUT displays the following message when the upgrade completes:
      Operation completed with exit status 0
      Output for this script (swupgrade) can be found at /var/opt/teradata/TDput/fileservice/logs/swupgrade.log
    3. Press Ctrl+c to exit the tail command.
    4. Type rpm –qa|grep DM and verify the Data Mover version was upgraded correctly.
  8. To upgrade additional agents in a multi-node Data Mover system, do the following:
    1. Copy the Data Mover upgrade bundle to instances in the /var/opt/teradata/packages/AgentUpgrade directory.
    2. Untar the bundle:
      # tar xzvf tdm-linux-upgrade__sles11sp3_x8664.XXXXXXX-1.tar.gz
      # tar xzvf tdm-linux__linux_indep.XXXXX-1.tar.gz
    3. See Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers to upgrade a Data Mover agent on the Linux Teradata server.