Uninstallation Script Overview - Teradata Tools and Utilities

Teradata® Tools and Utilities for Linux Installation Guide Amazon Linux 2, CentOS, OEL, RedHat, SLES, Ubuntu - 17.20

Deployment
VantageCloud
deployment
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Tools and Utilities
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
trg1641290463177.ditamap
dita:ditavalPath
bbv1473194095470.ditaval
dita:id
ems1473187628189
Product Category
Teradata Tools and Utilities

If you have an earlier version than 15.10.10 of Teradata Tools and Utilities installed, use the uninstallation script uninstall_ttu.sh before you install a new version.

If you have a 15.10.10 or later version of Teradata Tools and Utilities installed, you have to option to keep or remove that release before installing 17.20 (for more information, see Multi-Version Support).

The script uninstalls dependency packages in the correct order.

The script is located on the installation media in the root directory.

Run the uninstallation script before you do either of the following actions:
  • Remove Teradata┬« Tools and Utilities products
  • Decommission Teradata┬« Tools and Utilities on a particular system
It is not necessary to uninstall previous versions of Teradata Wallet before you install another version of it. For information about retaining data in Teradata Wallet, see About Retaining and Deleting Data in Teradata Wallet.
The version of the following products that use Teradata Wallet and the version of Teradata Wallet must match:
  • Teradata Call-Level Interface version 2
  • Open Database Connectivity (ODBC) Driver for Teradata

When you run the script, you can specify individual packages to be uninstalled. Teradata recommends uninstalling the dependency packages (CLIv2, PIOM, and TDICU) last; however, they can be uninstalled individually regardless of the order.

If a dependency package is uninstalled without reinstalling a new version of that dependency package, the products that depend on that package stop functioning. For example, if CLIv2 is uninstalled, all products that depend on CLIv2 stop functioning. You are prompted to verify you want to uninstall it.

The script does not require any parameters to execute. When the script runs, all information within the script is displayed.

The script uses system packaging commands to uninstall packages, so it must be executed as root (or with root privileges).