Alerts Tab - Teradata Unity

Teradata Unity User Guide

Product
Teradata Unity
Release Number
16.00
Published
March 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
ipb1476817227329.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2520
lifecycle
previous
Product Category
Analytical Ecosystem

The Alerts tab shows all alerts raised on Teradata systems configured for Unity management. The Alerts tab updates by default each minute.

Alert Report
Each alert includes the following information.
Column Description
ID Unique identification number of an alert.
Code Code number of the alert triggered by the operation.
Type Code for type of alert.
Severity Indicator of the severity level of the alert. The Dashboard uses the following alerts:
  • indicates the severity level is critical and requires the attention of an administrator. The critical threshold is typically pre-configured by the administrator.
  • indicates a warning. A warning alert is a notification that the severity level has exceeded configured thresholds and is approaching critical.
  • indicates a normal condition. Normal alerts are provided for information purposes only and do not require administrator intervention.
Category Category assigned to the alert. Each alert is classified into one of these categories:
  • CFG: Configuration alerts related to the configuration of Unity; for example, errors that occur in the Unity configuration file.
  • CONS: Consistency alerts related to data consistency across Unity-managed Teradata Database systems; for example, a database placed in the Unrecoverable state due to data mismatch.
  • DBO: Database Operation alerts related to errors encountered by the Teradata Database system and sent to Unity; for example, a failed logon attempt.
  • HA: High Availability alerts related to the high-availability configuration of Unity; for example, if the Sequencers in a dual-system configuration are not in peer states, an alert is raised.
  • MGMT: Management alerts related to errors that occur in Unity management operations; for example, if Unity is unable to suspend the Teradata Database server.
  • SYS: System alerts related to management operation failures and general failures within the Unity environment (not including SQL errors); for example, errors due to loss of a connection to the Teradata Database server.
Description Brief statement about the alert condition
Raised at Timestamp the alert was generated.
Cleared by User logged on who cleared alert.
Resource Type Process where alert occurred. Processes are SEQUENCER, DISPATCHER, WATCHDOG, and ENDPOINT.
Process Specific name of process. For example, active_seq.
Region Name of region where the alert occurred.
Operation ID Unique identification number of the operation which raised the alert. You can click the ID to view operation details. For those alerts which are not associated with an operation, the field display is empty.
Repeat Count Number indicating how many times the identical alert has been raised. If the alert is raised more than once, the count increments. First-time alerts are set to 0 (zero). This count then updates based on the number of times the alert is raised.
Critical alerts displayed in the Alerts view are sent to Teradata Global Support. If Teradata Ecosystem Manager is configured with Unity, the alerts are also sent to the Teradata Ecosystem Manager.