Activities Performed During the Upgrade - Teradata Database

Teradata Database Node Software Upgrade Guide: Overview and Preparation

Teradata Database
Release Number
July 2017
English (United States)
Last Update
Product Category

The activities performed during an upgrade can vary depending on the type of upgrade you're performing (major/minor versus maintenance/patch) and whether you are using VM&F. Most of the steps are done manually with the exception of PUT's Install/Upgrade Operation.

The table below shows which activities may be used during an upgrade. They are generally listed in the order in which they are performed, but the order may change depending on the upgrade specifics. See the specific Teradata Database Upgrade Guide for more information and task instructions.

Activity Description
Finish Load/Unload operations Checks to make sure all load and unload data transfer jobs are completed or stopped before an upgrade can be performed.
Run pre-upgrade preparation script Combines several inspections into one convenient script. It inspects the Teradata Database to find problems that could interrupt the upgrade. It also runs the queries needed for the Upgrade Estimator Tool.
Save DBQL log data Saves existing log data to a new user table before the upgrade so that they are preserved afterwards.
Save RSS data Saves Resource Sampling Subsystem (RSS) tables which will be re-created during the normal upgrade process.
Save crashdumps Saves crashdumps from the CRASHDUMPS database. Existing crashdumps tables will not be compatible with the new release and cannot be used after the upgrade.
Set node windows for reboot Monitors node reboots on systems.
Verify BAR utilities are not running Verifies that Backup and Recovery (BAR) utilities are not running during the upgrade.
Run PUT's Install/Upgrade Software Operation Runs a program that performs many of the required upgrade steps without manual intervention. There is some manual interaction with PUT during the operation, but most of the activities are performed by PUT without interaction.
Bring down TDPs (start of system downtime) Applies only to a host with a Channel connection. Stops the Teradata Directory Programs (TDPs) running on the mainframes or network so that the system is completely quiescent and isolated before doing a reboot.
Bring up Teradata Database Starts the database so that the conversion preparation script in the PUT DBS Conversion Prep screen can be run.
Check for table locks Verifies that the DBS is quiet and ready for the upgrade.
Verify no pending operations Verifies that there are no load/unload data transfer jobs running.
Conversion preparation and reboot (point of no return) Runs the conversion preparation script from PUT's DBS Conversion Prep screen where the system is rebooted.
Monitor node reboots Watches the nodes as they reboot.
Verify running versions Verifies that the correct versions of PDE, DBS, RSG, TGTW, HOST, and TDGSS are running.
Converting the DBS Starts the PDE on the new Teradata Database version (for major/minor only).
Verify new versions Verifies that the correct versions of PDE, DBS, RSG, TGTW, HOST, and TDGSS are running, that the PDE is in TPA state and that the system is quiescent.
Running Database Initialization Program (DIP) Installs the new patches of this upgrade into the Teradata Database. For major upgrades the DBS conversion script runs DIP automatically; DIP must be run manually for minor, maintenance, and efix upgrades.
Restarting the DBS after DIP Starts the DBS after you run DIP.
Upgrade channel adapter firmware Stops the DBS, installs new channel device firmware, then starts PDE and the DBS again.
Run SCANDISK Runs the SCANDISK utility.
Run CheckTable Runs the CheckTable utility.