The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 10198 Views
- Wipro, I also Faced
- E-Mail Answers
Answer / 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 |
How many codd's rules are satisfied by teradata database?
any one answer me how they can analyzing the project using data ware housing?
Why Multiload and Fastload does not supports SI,JI,RI and TRIGGERS?
what is identity columns in TD?
During the Display time, how is the sequence generated by Teradata?
What are the string manipulation operators and functions associated with teradata?
why should we go Teradata over Oracle,what is the main differences?
What are the design features involved in teradata?
What are the various etl tools in the market?
Where we use PPI in real time??? What is the disadvantages of PPI?
Explain the teradata primary index mechanics in detail with a diagram.
what is single value and Multivalue ?
Teradata 
