Upgrading Data Mover

Prerequisite

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.

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.
Log in as user root 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.
1. Copy the tdm-linux-upgrade__sles11sp3_x8664.XXXXX-1.tar.gz to /var/opt/teradata/swupgrade-source.
2. Untar the following:
```
# tar xzvf tdm-linux-upgrade__sles11sp3_x8664.XXXXXXX-1.tar.gz
# tar xzvf tdm-linux__linux_indep.XXXXX-1.tar.gz
```
3. Type ./build_dsainputs -d to create the /tmp/dsainputs file.
4. Verify if there is at least 100 GB in the Data Mover repository on the Data Mover master node to dedicate to DSC.
5. 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.
6. In the Data Mover master node where DSC is installed, type uname -n to obtain output.
7. 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:
1. 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
```
    It is recommended to change the dbc password back to the original password once the upgrade is successful.
  The upgrade process begins, displaying progress messages on screen until the system reboots.
2. 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
```
3. Press Ctrl+c to exit the tail command.
4. Type rpm –qa|grep DM and verify Data Mover version is upgraded properly.
To upgrade additional agents in a multi-node Data Mover system, do the following:
1. Copy the Data Mover upgrade bundle to instances in the /var/opt/teradata/packages/AgentUpgrade directory.
2. Untar the bundle:
```
# tar xzvf tdm-linux-upgrade__sles11sp3_x8664.XXXXXXX-1.tar.gz
# tar xzvf tdm-linux__linux_indep.XXXXX-1.tar.gz
```
3. See Teradata Data Mover Installation, Configuration, and Upgrade Guide for Customers to upgrade a Data Mover agent on the Linux Teradata server.

Upgrading Data Mover

Upgrading Data Mover

results matching ""

No results matching ""