The transaction exceeded the maximum number of rowhash locks allowed
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 |
can we load 10 millions of records into target table by using tpump?
What is difference between user and database in teradata?
How do you set the session mode parameters in bteq?
What is spool space and when running a job if it reaches the maximum spool space how you solve the problem?
Difference between client character set and server character set? What is the use of these two?default character set in teradata?
What is Difference b/w PI & PPI?how to implement PPI?
Highlight the limitations of TPUMP Utility.
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
If table have access lock.In the same table write lock is posible or not?
Hi send me the Teradata dumps to my id rajeshanantha@yahoo.co.in Thanks Rajesh. A
What is the maximum number of dml can be coded in a multiload script?
Explain teradata utilities. What is multiload, fast load, tpump?