Diagnose and resolve lock problems with DB2 for Linux, UNIX, and Windows

This article discusses lock waits, deadlocks, and escalations, and tells you how to monitor them, and what to do about them using DB2® for Linux, UNIX, and Windows. Sample monitoring scripts are included.

Bill Wilkins (wilkins@ca.ibm.com), Partner Enablement, IBM Information Management, IBM Canada

Bill Wilkins is a senior technical specialist in the IBM Business Partner Technical Enablement group in Toronto. Prior to this he worked in DB2 performance analysis in the IBM Toronto development laboratory for six years. He is an IBM Certified Advanced Technical Expert in DB2 UDB, has contributed to several books on DB2, and has over twenty-six years of experience in the IT industry.



Yasir Warraich (warraich@ca.ibm.com), Database Consultant, IBM Canada

Author Photo: Yasir WarraichYasir Warraich is a database consultant from the IBM Toronto Laboratory and works primarily with IBM Business Partners. Yasir has worked at IBM for nine years, eight years in DB2 Advanced Technical Support, and the other one as a consultant specializing in database performance tuning and migrations from other RDBMS to DB2.



12 February 2007 (First published 01 October 2003)

Also available in Russian

Overview

If performance is an issue with your database, it's vital to understand the issues surrounding row and table locking. This article is a "how-to" guide for dealing with issues related to locking in DB2 Universal Database.

Topics covered include:

  • The tools for monitoring locks
  • Resolving lock issues and reducing locking
  • Avoiding lock escalations
  • Resolving lock waits
  • Resolving deadlocks
  • Locking notes specific to partitioned databases
  • A case study
  • Sample scripts and monitoring output

Download

DescriptionNameSize
Read the full article (PDF) here:0310wilkins.pdf120KB

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Information management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=86819
ArticleTitle=Diagnose and resolve lock problems with DB2 for Linux, UNIX, and Windows
publish-date=02122007