DB2 - Problem description
Problem IC95178 | Status: Closed |
REORG WITH ALLOW WRITE ACCESS CAN LEAD TO INDEFINITE LOCK WAIT WITH CONCURRENT TABLE ACTIVITY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
A REORG with ALLOW WRITE ACCESS option should allow for concurrent write activity on the table. At the beginning of the reorg operation, the reorg will wait for existing write transactions on the table to complete before proceeding. This should not block new write on the table, however in a rare locking situation, involving static SQL accessing the table as well, it's possible that the static SQL transaction waits behind reorg indexes. When the transaction(s) holding the table lock commits, the transaction waiting behind the reorg will be allowed to proceed. This is related to the fix for APAR IC81464 that was introduced in V9.7 Fix Pack 6. The reorg session will show that it is trying to convert a lock with stack : sqloWaitEDUWaitPost IntrptWaitLock sqleIntrptWaitLock sqlplfnd sqlplfnd sqlpUpgradeLock sqldCreateIndex sqldIndexCreate sqlrreorg_index_obj sqlrreorg_indexes sqlrreorg_sendinfo sqlrr_reorg_indexes | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7.0.9. * **************************************************************** | |
Local Fix: | |
Do not use the "allow write access" reorg option | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 version 9.7.0.9. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC95753 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.08.2013 17.12.2013 30.09.2015 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.0.9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |