Upgrading Teradata Components Other than Data Mover and Server Management

Before starting, open a maintenance window to see the status of the Teradata components during the upgrade process, including data, summary alerts, and reports. See Teradata Server Management Web Services User Guide.
After initiation, the upgrade process is completely non-interactive. During the upgrade, PUT reboots the system.

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

When the software upgrade script runs as a part of the following procedure, it creates a temporary d2.xlarge instance and a 350 GB EBS volume. This instance and volume is automatically deleted, but you will incur a charge of less than $1.00. Software upgrades are stored in an AMI in your account for node failure recovery purposes or if you use the Unfold feature. Charges for this AMI vary per customer.

  1. Download the required upgrade bundles.
    Because the operating system upgrade bundle includes both important security updates and the latest version of PUT, you must upgrade the operating system whenever upgrading other Teradata components in a virtual or public cloud environment.
  2. Log in as user root to the system where the component you are upgrading is installed.
  3. If the following directory does not exist, create it:
  4. Transfer the downloaded upgrade bundles to /var/opt/teradata/swupgrade-source.
  5. Change to the PUT bin directory:
  6. 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, set your dbc password to dbc and run the command:
      # /opt/teradata/TDput/bin/swupgrade -U
    The upgrade process begins, displaying progress messages on screen until the system reboots.
  7. Log back on to the system and run the command to display the log as the upgrade completes:
    tail -f /var/opt/teradata/TDput/fileservice/logs/swupgrade.log
    PUT displays the following to indicate upgrade completion:
    Operation completed with exit status 0
    Output for this script (swupgrade) can be found at /var/opt/teradata/TDput/fileservice/logs/swupgrade.log
  8. Press Ctrl+c to exit the tail command.
  9. Confirm the upgrade version on the system.
  10. Stop the database.
    # tpareset -x -y Stop for swupgrade
  11. Run the software upgrade script on a single node, regardless of the number of nodes in your configuration.
    # tdc-nodestart-post-swupgrade --bynet-name byn001-02

results matching ""

    No results matching ""