Interested to Buy Any Domain ? << Click Here >> for more details...
The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 11214 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
Explain fallback in teradata?
What are teradata utilities?
In Teradata, how do we Generate Sequence?
What is the purpose of joins in teradata?
What are the updated features of teradata?
Describe primary index in teradata?
List the logical and conditional operators that are used with teradata along with their meanings?
What tools would you use for that?
What is the function of parser component in teradata?
What is meant by a Parsing Engine?
How is the teradata different from oracle?
What is spool space?
Why managing the data is important?
What are the string manipulation operators and functions associated with teradata?
If I wanted to run a TPump job only once per day - basically working on a file that is produced once per day - how would you set up the parameters for that sort of job ?
