DB2 - Problem description
Problem IC66177 | Status: Closed |
RUNSTATS GENERATES EXCESSIVE LOCKING IN SYSCOLUMNS AND LOCK TIMEOUTS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Running runstats at the time other DDL modifying statements are running will likely encounter lock timeouts or deadlocks. The investigation revealed that the lock contention are on object that are not related to the RUNSTATS. Applications running alter, drop or create table will timeout or wait until runstats completes giving the impression that they are hung. They will be waiting for locks held by the application running runstats on another table. The isolation level used to update columns fro runstats is RR and therefore it will lock rows in SYSCOLUMNS that are not related to the table being updated. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * Processes will lock timeout when runstats is * * executing.Normally processes that do DDL on other objects * **************************************************************** * RECOMMENDATION: * * Upgrade to v97 fp2 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Fixed in v97fp2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.02.2010 25.05.2010 25.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |