The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 9915 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 is a pseudo key? What is its use???
What are the functions performed by bynet?
What are the functions of a teradata dba?
Explain fastload in teradata?
where we can use the delimiter in mload? pls let me know
what do you mean by INMOD Routines and OUTMODE Routines ?
On which column will you take primary index???
What are the things to be considered while creating secondary index?
Describe primary index in teradata. And what are the available primary index types?
which join mostly use in realtime?
What is a three-tier data warehouse?
How to copy teradata scripts from ur remote desktop to server machine?
Teradata 
