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 have an unconnected lkp to lookup a DB2 record against a Teradata record?
In Teradata, how do we Generate Sequence?
How to handle nulls in Teradata??? How many columns can be there in a table??? How to find average sal with out using avg function????
How do you create tables? Exact syntax, and create profiles, users in teradata?
Explain the term 'database' related to relational database management system?
What is spool space? Why do you get spool space errors? How do trouble-shoot them?
what is use of fload loading into set table?
How will you solve the problem that occurs during update?
What is meant by a Channel Driver?
What is partitioned primary index (ppi)?
What do you mean by tpt in teradata?
What are the different design perspectives used in teradata?