16.10 - Uninstallation Script Overview - Teradata Tools and Utilities

Teradata Tools and Utilities for Microsoft Windows Installation Guide

prodname
Teradata Tools and Utilities
vrm_release
16.10
created_date
April 2018
category
Installation
featnum
B035-2407-048K

It is not necessary to uninstall previous versions of Teradata Wallet before you install another version of it.
The uninstall_TTU.vbs should only be used to remove pre-14.10 products. The Add/Remove entry for the 14.10 or later Suite or the Suite silent_uninstall.bat file should be used to remove the Suite. The script is in the installation package at:
  • \Windows\uninstall_TTU.vbs
It creates a log file that contains a record of all of the steps taken during execution.
  • %TEMP%\uninstall_script_timestamp.log
msi logging is turned on during package installation. The msi uninstallation log files are stored in the %TEMP% folder with the following file name:
  • uninstall_package_name_package_version.log

These logs provide useful information to support personnel if any issues are observed in the uninstallation of Teradata Tools and Utilities packages.

Run the uninstallation script before you do any of the following:
  • Install a new version of a package
  • Install a specific version of a package (a version other than the latest version)
  • Decommission Teradata Tools and Utilities software on a particular system
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 products (CLIv2, PIOM, TDICU, TDODBC, and TeraGSS) last; however they can be uninstalled individually regardless of the order.

If a dependency product is uninstalled without reinstalling a new version, the products that depend on that product stop functioning. For example, if CLIv2 is uninstalled, all products that depend on CLIv2 stop functioning.
In order for the script to run, the command must include the PRODUCT parameter. Without it, the script displays usage information. The script supports the following two options:
  • /PRIORTOVERSION
  • /FORCE

As an argument to the script, a version can be specified using the /PRIORTOVERSION parameter (for example: /PRIORTOVERSION:14.10.00.00 ). The uninstallation script only uninstalls versions of the specified packages that are earlier than the version specified in the /PRIORTOVERSION parameter. When the /PRIORTOVERSION parameter is not specified, the default value is /PRIORTOVERSION:16.00.00.00.

The default behavior handles uninstallations of Teradata Tools and Utilities packages, except corrupted installations which are handled using the /FORCE parameter. When this parameter is specified, the uninstallation script performs an extensive registry search for all versions and components that were installed by a particular Teradata Tools and Utilities package. If the registry entries are found, the script deletes them. This parameter should be used with care because it takes time to search the registry for versions and components of a package. If multiple packages are passed as arguments, the script can take a long time to run.

When both parameters are specified, the /FORCE:TRUE parameter performs uninstallation and cleanup of only the versions of the packages that are earlier than those specified using the /PRIORTOVERSION parameter. The /FORCE:TRUE should not be used initially. If a product does not get uninstalled without using the FORCE flag, then use it only when a product or list of products are specified.

The script uses system packaging commands to uninstall packages, so it must be executed by an admin user (or by someone with admin privileges) .