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
How to find duplicates in a table?
What are the different table types that are supported by teradata?
What is the use of fallback?
What are the advantages of teradata?
What is bteq utility in teradata?
What is the purpose of joins in teradata and what are the available join types?
How teradata makes sure that there are no duplicate rows being inserted when its a set table?
What are the things to be considered while creating secondary index?
List the logical and conditional operators that are used with teradata along with their meanings?
How to identify ppi columns?
Why do you get spool space errors? How do trouble-shoot them?
What is the basic syntax for teradata select statement?
What is the meaning of Caching in Teradata?
What are the commands to make a new table, change a table and remove a table in teradata?
What is meant by a dispatcher?