Configuration Mode - Parallel Upgrade Tool (PUT)

Parallel Upgrade Tool (PUT) Reference

Parallel Upgrade Tool (PUT)
Release Number
February 2020
English (United States)
Last Update
Product Category
Teradata Tools and Utilities

For the Configure Teradata Vantage operation, the following Configuration modes are available:

Configuration Mode Description
  • PUT generates a working Vantage configuration automatically, based on your default criteria.
  • Most automated and recommended way to install. This mode uses predefined default settings to configure your system.
  • Allows you to change the default settings and installation directory.
    Does not provide a final review of the configuration before it is generated.
Teradata requires you to be an expert Teradata user before selecting Custom configuration mode.
  • Custom configuration mode is used for configurations that fall outside the defaults of Typical mode.
  • PUT selects the most current version of software.
  • Specify options and be review the proposed configuration at several points during the process.
Rebuild Vconfig File Only
  • Allows you to update the format/settings in the vconfig.txt (Linux) file.
Rebuild Vconfig File and Run Sysinit
  • Bring the system back to its original state when PUT first brought it up.

Typical Configuration Defaults

The Typical configuration mode of the Configure Teradata Vantage operation is the most automated and recommended way of configuring Teradata. The following list describes how PUT works to help you understand where to modify settings if necessary.

  • PUT uses all available Teradata storage to configure Vantage
  • There are a fixed number of vprocs (virtual processors).
  • All selected nodes running Vantage are used for Vantage configuration.
  • Unassigned disk partitions are assigned as pdisks (physical disks). "Unassigned" means the partition has no drive letter assigned, it has a size greater than or equal to 10 MB, and is not a boot, diagnostic, or mirror partition. For multi-node cliques, only shared storage is used for pdisks. For single-node cliques and SMP systems, both internal and external storage are used, if available. For Linux, unassigned (available) partitions are those of type "00" (EMPTY) or type "0xda" (Teradata) partitions.
  • The number of AMPs is determined by AMP balancing. Node-IDs are assigned based on disk type.
  • PUT creates one PE and one Gateway vproc for each TPA node in the system.
  • PUT creates one additional PE vproc for each IBM Host Channel in the system.
  • For each LUN that has no partitions, PUT will create an appropriate number of partitions based on configuration guidelines.
  • For Teradata Database systems (release 12.5 or later) using Teradata Smart Storage Services (TSSS), AMP Affinity is set to 100. This corresponds to traditional Teradata storage handling.

Custom Configuration Prerequisites

At a minimum, you should be familiar with Teradata Concepts prior to running the Configure Teradata Vantage operation. If you plan to use the Custom configuration mode, you must know the configuration you want to create. Answer the questions below prior to running the Configure Teradata Vantage operation in Custom configuration mode:
  • How many AMPs per clique?
  • Are the AMPs going to be movable?
  • How many LAN entries per node?
  • How many pdisks per AMP?
  • Which pdisks should be assigned to which AMPs (if you have a particular order)?
  • If using IBM Channel adapters, what are the CUA and hgid values and how many PE vprocs should be created for the channels?
  • Are there storage arrays where volumes need to be created?
  • If there are storage arrays, what RAID level and striping is desired?
  • What is the number of LUNs to create per drive group? Creating LUNs could take several hours.
  • How many partitions need to be created for each LUN?

Rebuild Vconfig File Only

The Rebuild Vconfig File Only option is similar to the vconfig -r option. Rebuild Vconfig File Only is useful when your sole purpose in running the Configure Teradata Vantage operation is to update the format/settings in the vconfig.txt (Linux) file (for example, when upgrading to a newer version of Vantage). A valid, existing configuration is required to run this option. This option is unavailable for a new system or a system where no valid configuration currently exists.

Rebuild Vconfig File and Run Sysinit

When you want to return the system to its original state when PUT first brought it up. Content of vconfig is not changed; PUT only rebuilds the vconfig. If the clustering is not the same as PUT standard clustering, PUT prompts you to either allow PUT to reset the clustering to the PUT standard cluster or abort the operation. If you decide to reset the clustering, PUT runs the Run Config and Reconfig steps to apply the new changes. Because sysinit is run, all the associate GDOs that are part of sysinit are changed.

  • This option is unavailable for a new system. PUT issues an error at the GDO Info step.
  • This option requires the database to be down.