The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 9938 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
In Teradata, what is the significance of UPSERT command?
What is logical data model?
Did you write stored procedures in teradata?
What are the main components of teradata system?
What is the difference between global temporary tables and volatile temporary tables?
What is a node in teradata? Explain
What are the different table types that are supported by teradata?
What is difference between user and database in teradata?
hi frnds i want to learn teradata utilities and teradata dba real time. i have 1+ years of experience in teradata. so i want to go deeply in Tearada. plz let me know at my email id who r best to learn from. im lookng for a realtime guy in HYD or Banglr. Thanks in advance. Rajesh my email-id: rajeshmss87@gmail.com
What is the particular designated level at which a LOCK is liable to be applied in Teradata?
What is the maximum number of dml can be coded in a multiload script?
What is upsert statement in teradata?
What is the primary index in teradata?
What can be achieved by using the teradata rdbms?
What are the various etl tools in the market?
