Elapsed Time or Blocked Time Considerations - Advanced SQL Engine - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

Product
Advanced SQL Engine
Teradata Workload Management
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
nbl1556236178169.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1197
lifecycle
previous
Product Category
Software
Teradata Vantage

The Change Workload to: action is not available for the Elapsed Time or Blocked Time exception criteria. The purpose of changing a workload is to put a request where it belongs in the priority hierarchy. Temporary system-wide conditions cause a request to be blocked or run too long. These exceptions do not occur because the request is out of character for the workload.

Elapsed Time or Blocked Time exceptions are better suited to an automated alert. Then the DBA can investigate the system-wide situation and resolve the problem by identifying the cause of the slowdown, rather than punishing the requests suffering from the situation.