This procedure is for upgrading the operating system bundle only. It does not apply to upgrading the database software or Teradata ecosystem software.
After initiation, the upgrade process is completely non-interactive. During the upgrade, the system is restarted.
When performing a major upgrade, such as from a SLES 11 to a SLES 12 version, you must redeploy the system.
- Set a maintenance window. See Using Maintenance Windows.
- Go to https://support.teradata.com, log on, then download the bundle.
-
Connect to the PDN node of the Teradata system and switch to the root user environment.
# sudo su -
-
If the following directory does not exist, create it:
# mkdir /var/opt/teradata/swupgrade-source
- Transfer the downloaded upgrade bundles to /var/opt/teradata/swupgrade-source.
-
Check your version of TDput.
# rpm -qa | grep -i TDput
If the TDput version is earlier than 03.09.06.03, you must upgrade TDput on all nodes. See https://knowledge.teradata.com/KCS/id/KCS004693
-
Run the swupgrade -U command:
/opt/teradata/TDput/bin/swupgrade -U
Progress messages appear on the screen. -
If your system has more than one node, shut the database down and make a backup image that can be used for elasticity operations, node failure recovery, or other purposes.
You can specify any node in the tdc-nodestart-post-swupgrade command below other than the node you are logged into. This command makes a backup image of the node you specify to be used for node failure recovery or scale out operations.
-
Check the database state to see if it is down.
# pdestate -a
-
If the database is not already down, shut it down.
# tpareset -x
-
Type the following command:
# tdc-nodestart-post-swupgrade -–bynet-name byn001-02
where byn001-02 is the node you are copying.
-
Start the database.
# /etc/init.d/tpa start
-
Check the database state to see if it is down.
-
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.