6.02 - Scaling Up or Scaling Down VM Sizes - Teradata Software for Azure

Teradata Vantageā„¢ on Azure (DIY) Installation and Administration Guide

Teradata Vantage on Azure
Release Number
Release Date
January 2019
Content Type
Publication ID
English (United States)
  • To perform this procedure, you must be assigned the Contributor role.
  • [BYOL only] You must have a valid, active license with sufficient TCore for a scaled up system.
You can scale a Teradata Database up or down by changing the VM sizes in the system. Be sure to scale only supported VM sizes.
Scaling unsupported VM sizes may impact database performance. Data loss will occur if scaling local storage VM sizes.
  1. [BYOL only] Revoke the license.
  2. Stop the database.
    # tpareset -x stop system
  3. Run the following command on all nodes to confirm the database is down.
    # pdestate -w
  4. From the Azure portal, click Stop on every VM.
  5. Scale the VMs up or down.
    1. From the Azure portal, locate the Teradata Database resource group.
    2. For each deallocated VM, under the Settings pane, click Size and choose a different VM size. Select a VM that supports the number of drives you attached to your VM. You will get an error if you select a VM size that supports fewer drives.
    3. Verify all VMs were scaled.
  6. Start the VMs using one of these options.
    Option Actions
    Azure portal Use this option if you have a small number of VMs.
    1. From the Azure portal, locate the Teradata Database resource group.
    2. Locate each stopped VM and click Start.
    Azure CLI Use this option if you have a large number of VMs. Before proceeding, install the Azure CLI 2.0.
    1. From the CLI command prompt, type the following command:
      az vm start -n -rg
      • -n is the name of the Azure VM.
      • -rg is the name of the Azure resource group that contains the VM.
    2. Press Enter and repeat these steps until all VMs are started.
  7. Confirm your system is running.
    # pdestate -a
    If the PDE state shows RUN/STARTED on all VMs, you successfully scaled all VMs and can skip the remaining steps. If the PDE state shows DOWN/HARDSTOP on any VM, continue to the next step.
  8. Identify any failed AMPs and bring them back online.
    1. From Vproc Manager, type STATUS to identify any failed AMPs.
    2. Type the following to bring each AMP or a set of AMPs online: Set ### to ### online, where the first ### is the first AMP number and the second ### is the last AMP number. For example, set 0 to 10 online.
    3. Type QUIT.
    4. From the command line, stop the database.
      # tpareset -x
    5. Confirm the database is down.
      # pdestate -w
      PDE state: DOWN/HARDSTOP
  9. [BYOL only] Reactivate the license.
    1. Run the activate commands and follow instructions on the screen.
      sudo su -
      tdc-telm -m activate
      echo $?
      Zero (0) means the activation was successful; a number other than 0 means an error occurred.
    2. Run tdlem-util -r on all nodes:
      sudo su -
      tdlem-util -r
    3. Log into the Teradata EMS server at https://slem.teradata.com/ecp and verify the quantity of available TCores decreased by the number of activated TCores.
  10. Restart the database.
    # /etc/init.d/tpa start
  11. Confirm the database is running.
    # pdestate -a
    The PDE state should show RUN/STARTED on all VMs. If the PDE state shows DOWN/HARDSTOP, repeat the above steps for stopping and restarting the database.
    If the PDE continues to show DOWN/HARDSTOP, contact Teradata Customer Support.
  12. From Vproc Manager, type STATUS to confirm all AMPs are ONLINE.