The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 9916 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
How do you set the session mode parameters in bteq?
What are the functions involved in shared information architecture?
How to write the query . eid enm doj dob i want to display the names who worked more than 25 years .
What do high confidence, low confidence and no confidence mean in explain plan?
What is the command in bteq to check for session settings ?
Explain teradata utilities. What is multiload, fast load, tpump?
If RDBMS is halted what will you do ?
What is dimensional modeling?
What are different table types used in teradata?
How do you see a ddl for an existing table?
What is a clique?
When tpump is used instead of multiload?
What does Amp contain and what are all the operations that it performs?
How will you solve the problem that occurs during update?
How you will check the version of teradata?
