Upgrade the OS for the Database | Teradata Vantage on Azure (DIY) - 2.2 - Upgrading the Operating System for the Database - Teradata Vantage on Azure

Teradata Vantageā„¢ on Azure (DIY) Installation and Administration Guide

Product
Teradata Vantage on Azure
Release Number
2.2
Release Date
August 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-2810-071K
Language
English (United States)
This procedure is for upgrading the operating system bundle only. It does not apply to upgrading Teradata Database or Advanced SQL Engine itself, or to Teradata ecosystem software.

Contact your Service Experience Manager or Sales personnel with any upgrade procedure. Customers have to purchase Vantage Limited Upgrade plan and Success Tiers.

After initiation, the upgrade process is completely non-interactive. During the upgrade, PUT reboots the system.

When performing a major upgrade, such as from a SLES 11 to a SLES 12 version, you must redeploy the system.

  1. Set a maintenance window. See Using Maintenance Windows.
  2. Log on to https://support.teradata.com and download the bundle.
  3. Log on and switch to the root user of the system where the software you want to upgrade is installed.
  4. If the following directory does not exist, create it: /var/opt/teradata/swupgrade-source.
  5. If packages downloaded for earlier upgrades are still on the system, remove the files before downloading the upgrade bundle.
  6. Transfer the downloaded upgrade bundles to /var/opt/teradata/swupgrade-source.
  7. If the TDput version is earlier than 03.09.03.18, you must manually install TDput on all nodes. See https://knowledge.teradata.com/KCS/id/KCS004693
  8. Run the swupgrade -U command:
     /opt/teradata/TDput/bin/swupgrade -U
    Progress messages display on the screen.
  9. To verify the bundle was installed correctly, go to the file /var/opt/teradata/TDput/fileservice/logs/sequencer_simple-install.log and scroll to the Overall Package Install Status section.
    The Success column lists the number of nodes on which each package was installed. Check to see that the Fail column does not indicate any failures.
  10. Check the status of the database.
    # pdestate -a
  11. If the database does not come up by itself after a few minutes, start it manually.
    # /etc/init.d/tpa start