The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 10199 Views
- Wipro, I also Faced
- E-Mail Answers
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 the different design perspectives used in teradata?
What is primary index and secondary index?
How to eliminate product joins in a teradata sql query?
What is called partitioned primary index (ppi)?
What is teradata? What are some primary characteristics of teradata?
Explain the term 'columns' related to relational database management system?
What interface is used to connect to windows based applications?
Explain the term 'tables' related to relational database management system?
During the Display time, how is the sequence generated by Teradata?
What are the frequently used data types in teradata?
Differentiate primary key and partition key?
Explain the term 'foreign key' related to relational database management system?
How to explain project Architecture and flow in teradata interviews?Can please anyone help on this? Am new to teradata.
any one answer me how they can analyzing the project using data ware housing?
What are aggregate tables? How do you design them using teradata?
