Before you install a new version of Teradata Tools and Utilities packages, you must use the
uninstallation script, uninstall_ttu.sh, to uninstall previous
versions of the packages.
The script uninstalls dependency packages in the correct order.
The script is located on the installation media in the root directory.
When the uninstallation script is executed from the install script, it prompts you to
choose whether to uninstall packages from previous versions of Teradata Tools and Utilities and leave any currently
installed versions installed.
Run the uninstallation script before you do either of the following actions:
- install another version of Teradata Tools and Utilities (a version other
than the existing one)
- decommission Teradata Tools and Utilities on a
particular system
It
is not necessary to uninstall previous versions of Teradata GSS Client package before you install another version. When you
uninstall previous versions, configuration settings that you
might want to reuse are deleted.
In
order to use
Teradata Wallet, the version of the product that uses
Teradata Wallet and the version of
Teradata Wallet must match. This applies to the following products:
- 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 that you uninstall
the dependency packages (CLIv2, PIOM, TDICU, and TeraGSS) 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. In this case, the script warns you and asks if you are sure
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).