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 are normalization, first normal form, second normal form and third normal form?
Can we collect statistics on multiple columns?
What do high confidence, low confidence and no confidence mean in explain plan?
What happens when a node suffers a downfall?
Explain the term 'tables' related to relational database management system?
What are the multiload utility limitations?
Backup Script was blocked you are unable to archive the data now. how do you analyze it and where do you identify ?
How do you do backup and recovery in teradata?
What interface is used to connect to windows based applications?
What are the string manipulation operators and functions associated with teradata?
What is spool space and when running a job if it reaches the maximum spool space how you solve the problem?
What are the updated features of teradata?
What is the purpose of upsert command?
What are the various indexes in teradata?
What is bteq utility in teradata?