Revoking Licenses for BYOL - Teradata Software for Azure

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

Product
Teradata Vantage on Azure
Release Number
5.01
Published
July 2018
Language
English (United States)
Last Update
2018-07-18
dita:mapPath
kmk1523992471627.ditamap
dita:ditavalPath
TeradataAzure_PubCloud_5.01_5.01.01.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud

For BYOL, you must revoke the Teradata Database licenses or Teradata IntelliSphere licenses before you deallocate or delete a Teradata Database VM, or delete the Azure resource group. If you accidentally delete the resource group before you revoke the licenses, contact Teradata Customer Support.

Since licensing information is logged in the Azure diagnostic storage account named diag, it is important to keep the CanNotDelete resource lock on this diagnostic storage account to prevent diagnostic logs from being deleted.

  1. Switch to the root user environment.
    # sudo su -
  2. Run the following command from a Teradata Database node.
    tdc-revoke
    The revocation is complete when you see License has been revoked successfully.
  3. Verify the revoked licenses have been credited back.
    1. Log into the Teradata EMS server at https://slem.teradata.com/ecp.
    2. Click to expand Products.
    3. In the Available column, verify the quantity of available TCores has increased by the number of revoked TCores.
It is safe to deallocate the VM or delete the VM. You can also delete the resource group.