Skip to content

Having DB2 Lock Timeout Problems?

February 27, 2013

I know from time to time most applications experience lock timeout problems especially for new applications or when porting applications from other database platforms to DB2. By default, DB2 only reports on deadlocks and lock escalations. If you are running DB2 9.7, there is new capability to help you in resolving lock timeouts. You can enable this new support by setting the mon_lck_msg_lvl DB CFG parameter to 3. 1 is the default setting. This setting can be changed dynamically online, “db2 update db cfg for dbname using mon_lck_msg_lvl”. Once set to 3, additional lock timeout information will be captured and written to the admin notification log. Stay tuned!

From → Uncategorized

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: