15.10 - QryLogEventHisV - Teradata Database

Teradata Database Data Dictionary

Product
Teradata Database
Release Number
15.10
Content Type
Administration
User Guide
Publication ID
B035-1092-151K
Language
English (United States)

Query

DBC

 

View Column

Data Type

Format

Source Table.Column

ProcID

DECIMAL(5,0)

NOT NULL

-(5)9 (explicit)

TDWMEventHistory.ProcID (NUPI)

CollectTimeStamp

TIMESTAMP(6)

NOT NULL

YYYY-MM-DDBHH:MI:SS

TDWMEventHistory.BufferTS (NUPI)

EntryTS

TIMESTAMP(6)

NOT NULL

YYYY-MM-DDBHH:MI:SS.S(F)Z

TDWMEventHistory.EntryTS

EntryKind

CHAR(10) LATIN

NOT CASESPECIFIC

X(10)

TDWMEventHistory.EntryKind

EntryID

INTEGER

--,---,---,--9 (explicit)

TDWMEventHistory.EntryID

EntryName

VARCHAR(128)

UNICODE

NOT CASESPECIFIC

X(128)

TDWMEventHistory.EntryName

EventValue

FLOAT

----,---,---, ---,--9 (explicit)

TDWMEventHistory.EventValue

LastValue

FLOAT

----,---,---, ---,--9 (explicit)

TDWMEventHistory.LastValue

Activity

CHAR(10) LATIN

NOT CASESPECIFIC

X(10)

TDWMEventHistory.Activity

ActivityId

INTEGER

--,---,---,--9 (explicit)

TDWMEventHistory.ActivityId

ActivityName

VARCHAR(128)

UNICODE

NOT CASESPECIFIC

X(128)

TDWMEventHistory.ActivityName

ConfigId

INTEGER

--,---,---,--9 (explicit)

TDWMEventHistory.ConfigId

SeqNo

SMALLINT

ZZZ9

TDWMEventHistory.SeqNo

Spare1

VARCHAR(128)

UNICODE

NOT CASESPECIFIC

X(128)

TDWMEventHistory.Spare1

Spare2

INTEGER

--,---,---,--9 (explicit)

TDWMEventHistory.Spare2

Spare3

FLOAT

----,---,---, ---,--9 (explicit)

TDWMEventHistory.Spare3

Possible Values for Activity

 

Value

Description

ACTIVE

The Event...State is becoming active

INACTIVE

The Event...State is becoming inactive

EXPRESSION

The Event entry was used to determine that an expression is to be made active

SYSCON

The Expression entry was used to determine that a syscon is to be made active

OPENV

The Expression entry was used to determine that an openv is to be made active

Possible Values for EntryKind

  • EVENT
  • EXPRESSION
  • SYSCON
  • OPENV
  • STATE
  • The following is an example SQL statement that demonstrates how data can be extracted from the QryLogEventHisV view to give an explanation of the expression and events which caused a RED SysCon.

    WITH RECURSIVE
     CausalAnalysis(EntryTS,
             EntryKind, EntryID, EntryName, Activity, ActivityId) AS
     (
      SELECT EntryTS,
          EntryKind, EntryID, EntryName, Activity, ActivityId
      FROM DBC.QryLogEventHisV
      WHERE EntryKind = 'SYSCON'
        AND EntryName = 'RED'
        AND Activity = 'ACTIVE'
     UNION ALL
      SELECT Cause.EntryTS,
          Cause.EntryKind,
          Cause.EntryID,
          Cause.EntryName,
          Cause.Activity,
          Cause.ActivityId
      FROM CausalAnalysis Condition INNER JOIN
         DBC.QryLogEventHisV Cause
         ON Condition.EntryKind = Cause.ActivityId AND
          Condition.EntryID = Cause.ActivityId
     )
    SELECT *
    FROM CausalAnalysis
    ORDER BY 1 DESC;