Quantcast
Channel: Teradata Forums - All forums
Viewing all articles
Browse latest Browse all 27759

Failure 9128 The transaction exceeded the maximum number of rowhash locks allowed - response (1) by nhari

$
0
0
Hi, I also came across the same error today. Could find the details about this error in TD Error Messages pdf (1096) for v13.10. Pasting it here.     9128 The transaction exceeded the maximum number of rowhash locks allowed. Explanation: 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. Generated By: LOK subsystem. For Whom: End user. Remedy: Reduce the number of rowhash locks that the transaction is acquiring. An alternative is increase the General field ’MaxRowHashBlocksPercent’ value in DBSControl.   On the remedy part, I was able to understand increasing ’MaxRowHashBlocksPercent’ value in DBSControl but didn't understand how we can reduce the number of rowhash locks.   Please help.   Thanks in Advance Nirmal  

Viewing all articles
Browse latest Browse all 27759

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>