The transaction exceeded the maximum number of rowhash locks allowed
- 1 Answers
- 9888 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 do you mean by INMOD Routines and OUTMODE Routines ?
Explain fastload in teradata?
What are the different methods ot loading a dimension table? A fact table etc?
What are the types of tables in Teradata
22 Answers Cap Gemini, Cognizant, Infosys,
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 ?
how many modules are there in telecome domain?how to explain the architecture?
What is meant by a dispatcher?
What does sleep function does in fast load?
how do you manage the production space. what are the proactive methods you can take ?
how to delete duplicate records in multi set table without using any tables
2 Answers Accenture, Nest, South Nests Software Solution, Spiro Solutions,
in teradata level primary in table level allows duplicates why?
What is a node in teradata? Explain
Teradata 
