- Log on as root (or change to root and enter the root password).
- If a mount point directory does not exist, create one:
where mnt is the name of the media mount point.
- If the installation source files are not on the system disk, insert the appropriate media into the media drive.For a list of products and the media each one resides on, see DVD Contents.
- Mount the media device:
mount -V cdrfs -o ro /dev/media device name/mntFor example, if the media device name is c0t1d0, type:
mount -V cdrfs -o ro /dev/c0t1d0/mnt
- Change directory to the media mount point:
- Begin the installation process:
./setup.bat./setup.bat accepts command line options:A screen appears that:
- ./setup.bat a installs all packages and any required dependencies
- ./setup.bat bteq installs one package (in this example, bteq) and any required dependencies
- ./setup.bat arc bteq cobpp installs three packages and any required dependencies (you can specify as many package names as you want to)
- ./setup.bat 1 2 3 installs package numbers 1, 2, and 3 and any required dependencies (you can specify as many package numbers as you want to)
- Identifies the platform and media
- Lists numbered products that can be installed, the package version numbers, and package sizes
- Provides options for:
- Installing all software
- Removing previously installed software
- Displaying the sizes of the installed package
- Quitting the installation
- Select the packages to install.
If a selected package has dependencies, the script automatically installs the dependencies in the correct order.Software will be installed in the following order:
If Teradata Call-Level Interface version 2 (CLIv2) is installed before Teradata Wallet and if Teradata Wallet is installed using a different directory prefix than the default /opt, CLIv2 will not be able to use Teradata Wallet.
- Teradata GSS Client (teragss)
- Shared ICU Libraries for Teradata (tdicu)
- Teradata Call-Level Interface version 2 (cliv2)
- Teradata Data Connector API (piom)
- Other Products
- To avoid this situation, do either of the following:
- Install Teradata Wallet before you install CLIv2
- Install Teradata Wallet using the default directory prefix
- To rectify this situation, reinstall CLIv2.
For Teradata Wallet help, at the command prompt enter tdwallet help.
For more information about Teradata Wallet, see Security Administration, B035-1100.
- After reviewing product dependencies, do one of the following:
Command Action Install All Packages Type the letter a. The number of products selected appears in the bottom right corner of the screen. The packages selected for installation have an asterisk (*) beside them. Uninstall All Type the letter u. This removes previous versions of Teradata Tools and Utilities products.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. Install Selected Packages Type the numbers of the desired products and dependencies, separated by spaces, and press the Enter key.
- Dependencies: If individual products are to be installed, first determine the product dependencies, such as CLIv2 or Teradata Data Connector API (piom). Enter the numbers for the dependencies at the prompt, separated by spaces.
- Products: Enter the numbers for the products at the prompt, separated by spaces.
Quit Type the letter q to quit the installation.
- If you are prompted about retaining Teradata Wallet data, choose whether you want the uninstallation process to retain data or delete it:
Option Description Y (Yes) Data will be retained during uninstallation. N (No) Data will be deleted during uninstallation (if this is the last remaining version of Teradata Wallet to be uninstalled).
- Change back to the root directory.
- Unmount the media drive.
- Remove the installation media from the media drive.