Teradata Database Message 9128 - 9128 - Analytics Database - Teradata Vantage

Teradata® VantageCloud Lake - Analytics Database Messages

Edition
Lake
Product
Analytics Database
Teradata Vantage
Published
October 2022
Language
English (United States)
Last Update
2024-02-26
dita:mapPath
tzr1629746512312.ditamap
dita:ditavalPath
ft:empty
dita:id
vza1585613049811
lifecycle
latest
Product Category
Teradata® Vantage™
Message
The transaction exceeded the maximum number of rowhash locks allowed.
Explanation
This error is returned when a transaction has exceeded the number of rowhash locks allowed. The threshold on the number of rowhash locks allowed is defined in DBSControl via the General field 'MaxRowHashBlocksPercent'. This is done so that one transaction does not fill up the lock table with rowhash locks. The number of control blocks/locks that can fit into an AMP lock table is defined by STDMAXLOCKBLOCKS which is currently ~51860.
Generated By
LOK subsystem.
For Whom
End user.
Notes
None
Remedy
Reduce the number of rowhash locks that the transaction is acquiring. An alternative is increase the General field 'MaxRowHashBlocksPercent' value in DBSControl.