Interested to Buy Any Domain ? << Click Here >> for more details...
The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 11014 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 inner join and outer join?
What are the things to be considered while creating secondary index?
What are the types of tables in Teradata
22 Answers Cap Gemini, Cognizant, Infosys,
Explain the meaning of Amp?
What are the multiload utility limitations?
What are the primary characteristics of the Teradata.
Explain and compare pros and cons of start schemas?
Is it necessary to add? Quit statement after a bteq query when I am calling it in a unix environment?
What are types of partition primary index (ppi) in teradata?
During the Display time, how is the sequence generated by Teradata?
Why do you get spool space errors? How do trouble-shoot them?
What are different table types used in teradata?
Teradata 
