Open a maintenance window to see the status of the Teradata software during the upgrade process, including data, reports, and summary alerts.
After initiation, the upgrade process is completely non-interactive. During the upgrade, PUT reboots the system.
When performing a major upgrade, you must redeploy the system.
- Download the required upgrade bundles.
- Log in as the root user to the system where the component you are upgrading is installed.
- If the following directory does not exist, create it: /var/opt/teradata/swupgrade-source
- Transfer the downloaded upgrade bundles to /var/opt/teradata/swupgrade-source.
-
Create a dsainputs file.
For Teradata Data Mover 16.20 and later, DSC is installed and upgraded with Data Mover.
- Copy the tdm-linux-upgrade__sles11sp3_x8664.XXXXX-1.tar.gz to /var/opt/teradata/swupgrade-source.
-
Untar the following:
# tar xzvf tdm-linux-upgrade__sles11sp3_x8664.XXXXXXX-1.tar.gz # tar xzvf tdm-linux__linux_indep.XXXXX-1.tar.gz
- Type ./build_dsainputs -d to create the /tmp/dsainputs file.
- Verify there is at least 100 GB in the Data Mover repository on the Data Mover master node to dedicate to DSC.
- If there is not enough space in the Data Mover repository, update the BARSIZE property in the tmp/dsainputs file to less than 100 GB.
- In the Data Mover master node where DSC is installed, type uname -n to obtain output.
- Using the output, update the DSCNAME property in the /tmp/dsainputs file, using 22 alphanumeric characters or less.
- Change to the PUT bin directory: /opt/teradata/TDput/bin
-
For a single-node Data Mover system or a master node in a multi-node system, do the following:
-
Run the swupgrade -U command:
- If the TDput version is 03.09.01.07 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 03.09.01.07, change the dbc password from the repository to dbc and run the command:
# /opt/teradata/TDput/bin/swupgrade -U
We recommend changing the dbc password back to the original password once the upgrade is successful.
- If the TDput version is 03.09.01.07 or higher, set an environmental variable with your dbc password and run the swupgrade with the -d option:
-
Log on to the system and run this command to display the log as the upgrade completes: tail -f /var/opt/teradata/TDput/fileservice/logs/swupgrade.log
PUT displays the following message when the upgrade completes:
Operation completed with exit status 0 :: :: Output for this script (swupgrade) can be found at /var/opt/teradata/TDput/fileservice/logs/swupgrade.log
- Press Ctrl+c to exit the tail command.
- Type rpm –qa|grep DM and verify the Data Mover version was upgraded correctly.
-
Run the swupgrade -U command:
-
To upgrade additional agents in a multi-node Data Mover system, do the following:
- Copy the Data Mover upgrade bundle to instances in the /var/opt/teradata/packages/AgentUpgrade directory.
-
Untar the bundle:
# tar xzvf tdm-linux-upgrade__sles11sp3_x8664.XXXXXXX-1.tar.gz # tar xzvf tdm-linux__linux_indep.XXXXX-1.tar.gz
- See Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers to upgrade a Data Mover agent on the Linux Teradata server.