Monis,
Maybe there is some confusion around terminology, or how the delay functionality works:
Queries are not actually classified to throttle rules, queries only classify to workloads, which may or may not have throttles defined on them. And even if they have throttles, the throttles may not result in a delay for a given query, if the throttle counter is below the throttle limit.
Object throttles are associated to objects, and once the object throttle rules are activated, then queries that are associated to or reference those objects will be managed by the object throttle.
Only if a query is actually delayed by a throttle will the DelayTime column in DBQLogTbl carry a non-zero value. The act of classifying to a workload that contains a throttle does not cause anything to be reported in DelayTime.
If you have detected that a query has been delayed by a throttle, and have observed that the query has been placed in the delay queue, but DBQL does not report any time in DelayTime for that query, then it would be a good idea to contact Teradata Professional Services or the Support Center to help you resolve why that is happening and work with you on that issue. Unfortunately, that level of assistance is beyond what is possible within this forum. Maybe your object throttle definition is missing something, or pehaps the throttle rule is not activated appropriately. There could be many factors involved.
↧