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
What do you mean by parsing?
Define views in teradata with general syntax.
If a Node is busy what are the steps you can take to avoid ?
What interface is used to connect to windows based applications?
What are aggregate tables? How do you design them using teradata?
What is called partitioned primary index (ppi)?
What is basic teradata query language?
How do you do backup and recovery in teradata?
What is teradata and why it is used?
What is spool space? Why do you get spool space errors? How do trouble-shoot them?
What are the various indexes in teradata? How to use them?
Explain fallback in teradata?
What is the difference between union and union all in teradata?
How to eliminate product joins in a teradata sql query?
Difference between multiload and tpump?