Archives of the TeradataForum
Message Posted: Fri, 03 Apr 2015 @ 14:12:29 GMT
CPU is one thing to consider, for sure. But, you could also be out of I/O bandwidth or AWTs which can slow things down.
Your workload management settings could be set up to throttle the canary.
You could also have blocking from an archive or something that prevents the canary from running. (This would be my guess) Look for clues in DBQL for the canary queries. Is there a large amount of time between StartTime and FirstStepTime? Is there any DelayTime?
You can check the status of AWTs via the ResUsageSAWT table.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|