6.02 - Enabling Elasticity, Storage Expansion, and Node Failure Recovery - 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)
Enabling node failure recovery might result in losing diagnostic information while a failed node is stopped.
  1. Create a service principal.
  2. From the Azure portal, note the private IP and either the public IP or private DNS of the Teradata Database VM.
  3. Log on to the VM using the authentication type you chose when deploying the VM.
  4. Switch to the root user environment.
    # sudo su -
  5. Run the following command without arguments.
    # tdc-feature-init
  6. Enter the following information at the prompts:
    • client ID (application ID)
    • secret key (authentication key)
    • tenant ID (Active Directory ID)
    • subscription ID
    If successful, the output displays Credentials validation succeeded.

    Service principal details are written to /etc/opt/teradata/tdconfig/service_principal_config.json.

  7. [Optional] Check the following directories:
    • /var/log/boot.log (information)
    • /var/log/messages (messages)
    • /var/log/NFR/tdc-nodestart.log (node failure errors)