|
Problem IC66059
|
Status: Closed |
RUNSTATS GENERATES EXCESSIVE LOCKING IN SYSCOLUMNS AND LOCK TIMEOUTS |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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 for runstats is
Repeatable Read (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: *
* Runstats generates excessive locking. Application *
* willlocktimeout while trying DDL commands on objects that *
* arenotrelated to the runstats command *
****************************************************************
* RECOMMENDATION: *
* Migrate to v95fp6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in v95fp6 |
| Workaround |
not known / see Local fix |
| Comment |
FIN |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66177 IC66311
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.02.2010
22.06.2010
20.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
