|  | Level: Introductory Bill Wilkins (wilkins@ca.ibm.com), Partner Enablement, IBM Information Management, IBM Canada
Yasir Warraich (warraich@ca.ibm.com), Database Consultant, IBM Canada
01 Oct 2003
Updated 12 Feb 2007 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.
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 | Description | Name | Size | Download method |
|---|
| Read the full article (PDF) here: | 0310wilkins.pdf | 120KB | HTTP |
|---|
About the authors | | | 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 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. |
Rate this page
| |
|
