When a query is holding locks that are blocking other queries from completing, use the Blocking tab to gauge the impact of this blocking. By analyzing the number and type of queries blocked by this query, you can decide the best course of action to resolve the issue.
This information in this tab is read-only. The tab is available only when the selected query is blocking other queries and when connected to Teradata Database 15.0 and later. From the tab, you can drill down to view the details of the blocked session.
|Blocking Type||Indicates the significance of the blocker. Available values are:
|Blocking Count||Total number of sessions that are either directly or indirectly blocked by this session|
|Blocking Time||Amount of elapsed time that this session has been blocking other sessions, displayed as
|Blocking Impact||Blocked time summed together of each session that is either directly or indirectly blocked by this session, displayed as
|Blocking Locks||A comma-separated list of the locks that are responsible for the blocking, for example:
Granted write lock on table databaseName.tableName, Waiting on write lock on rowhash databaseName.tableName
The information displays in the following order:
|Session ID||Unique session identifier of the query that is blocking|
|Blocked Time||How long the query has been blocked, displayed as
|Username||Name of the user that is running the query that holds the lock|
|Workload||Name of the workload where the query is actively running|
|Query Band||String of key/value pairs of the query band for the session or transaction|