The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 9944 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 to run a query in teradata?
Highlight the differences between Primary Key and Primary Index.
How does hashing happens in teradata?
Explain PDE.
How to explain project Architecture and flow in teradata interviews?Can please anyone help on this? Am new to teradata.
What is the use of having index on table?
Explain BYNET.
why use references rather than pointers in the public api, particularly for arguments which are modified?
What are the different design perspectives used in teradata?
Explain Teradata performance tuning and optimization?
What are the different table types that are supported by teradata?
What is called partitioned primary index (ppi) and discuss the advantages of using it in a query?
Explain teradata utilities. What is multiload, fast load, tpump?
What are the multiload utility limitations?
What are the joins in teradata and how many types of joins are there in teradata?
