Logs - 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

Since licensing information is logged in the Azure diagnostic storage account named diag, it is important to create, set, and keep the lock level to CanNotDelete on this diagnostic storage account to prevent diagnostic logs from being deleted. A CanNotDelete lock level means users can read and modify a resource but cannot delete the resource. If your role is not Owner or User Access Administrator, see your company's cloud administrator to create a lock.

To view the status of scaling out and scaling in, access logs from the following locations.

Type Location
Azure diagnostic logs
  1. From the Azure console, go to the diagnostic storage account name that starts with diag.
  2. Look for the following: Blobs > teradata > FUF and access tdc_reconfig_timestamp.log to get the log of any operation.

A separate log is created each time you scale out or scale in.

System log file From inside the VM, view the following log for troubleshooting and diagnostics: /var/log/tdc-reconfig.log