The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 9919 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 |
what are the file sizes in your project?
How do you check the performance of Teradata Query and list down the basic Performance Tuning steps you use?
In Teradata, what is the significance of UPSERT command?
What is the diffrence between Multiload & Fastload interms of Performance?
What are tpump utility limitations?
How to run a query in teradata?
What are the functions of a Parser?
Hello Frndz, I have a table named product as shown below: product_id product_name 1 AAA 1 BBB 1 CCC 2 PPP 2 QQQ 2 RRR Now my output should be: product_id product_name_1 product_name_2 product_name_3 1 AAA BBB CCC 2 PPP QQQ RRR
How many types of joins are there in teradata?
how to delete duplicate records in multi set table without using any tables
2 Answers Accenture, Nest, South Nests Software Solution, Spiro Solutions,
How to view every column and the columns contained in indexes in teradata?
Explain Teradata performance tuning and optimization?
Teradata 
