Db2 Lock Info and Problem Determination
Recently I have been contacted by several clients reporting various degrees of lock-related problems in OLTP systems. One of the first item I check is the setting of the DB CFG locktimeout configuration parameter. What I find is that many times the default of -1 is used which doesn’t allow for any lock timeouts. This is one of the first parameters you will want to change, a value of 10000 (10 secs) is a good starting point. Additionally, make sure that you are taking advantage of the lock avoidance registry variables ( Covered in a future post). Here are a few links to some info to help you along the way with understanding Db2 lock isolation levels along with JDBC driver settings:
https://www.ibm.com/developerworks/data/library/techarticle/dm-1107db2isolationlevel/
Review the locktimeout setting here: https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.config.doc/doc/r0000329.html
Gunning Technology Solutions, LLC. THE WORLD LEADER IN Db2 LUW CONSULTING! 