Elapsed Time or Blocked Time Considerations - Teradata Workload Management - Database Engine 20

Workload Management User Guide - 20.00

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Database Engine 20
Teradata Workload Management
Release Number
20.00
Published
June 2025
ft:locale
en-US
ft:lastEdition
2025-11-20
dita:mapPath
gew1747088853217.ditamap
dita:ditavalPath
jlp1749501702948.ditaval
dita:id
icm1467243640567
Product Category
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.