The transaction exceeded the maximum number of rowhash locks allowed
Answer Posted / sughesh
This is error message for error :9128. 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.We can reduce the number of rowhash locks that the transaction is acquiring. An alternative is increase the General Field ’MaxRowHashBlocksPercent’ value in DBSControl.
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
Explain and compare pros and cons of start schemas?
List out all forms of LOCKS that are available in Teradata.
Explain some differences between mpp and smp?
What can be achieved by using the teradata rdbms?
What are the available join types in teradata?
What is node? How many nodes and amps used in your previous project?
What is a sparse index?
What is teradata? Also, list out some of the primary characteristics of teradata.
Explain the term 'database' related to relational database management system?
Can we collect statistics on multiple columns?
What is a node in teradata? Explain
What is collect statistics?
What are the frequently used data types in teradata?
What is teradata?
Explain amp in teradata?