6.02 - Upgrading Teradata Database from Releases Prior to 6.0 - 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)
  • Confirm the database is running.
    # pdestate -a
    PDE state: RUN/STARTED
  • Confirm the BYNET is running.
    # bam -s
Beginning in release 6.0, only one NIC is required to run Teradata Database. Use this procedure to convert existing VMs running on three NICs to run on one NIC.
  1. Create a service principal.
  2. Stop the database.
    # tpareset -x -f -y stop system
  3. Uninstall the previous tdc-azure-all package from all nodes.
    # rpm -qa|grep tdc-azure
    rpm -ef output of previous command
  4. Confirm the package was uninstalled from all nodes.
    # rpm -qa|grep tdc-azure*
  5. Copy the latest rpm package on each node.
    # scp rpm_name username@ip:/path
    If you copy the rpm package from one node to another node in the same VNet, you can use a private IP.
  6. Install the new tdc-azure-all rpm package on each node.
    # rpm -ivh path to rpm package
    Make sure the rpm resides in the same location on all nodes.
  7. Upgrade the network configuration from three NICs to one NIC.
    # tdc-singlenic
    where the output looks similar to the following example:
    SMP001-01: # tdc-singlenic
    adding IP to nic:databases3-nic00
    adding IP to nic:databases3-nic10
    adding IP to nic:databases3-nic20
    {33: u'', 34: u'', 35: u''}
    executing extension on database-vm0
    executing extension on database-vm1
    executing extension on database-vm2
  8. Rename tdc-nodestart-disabled to tdc-nodestart on each node.
    # mv /usr/local/bin/tdc-nodestart-disabled /usr/local/bin/tdc-nodestart
  9. Create SingleNICSupported on each node.
    # touch /etc/opt/teradata/tdconfig/SingleNICSupported