DB2 FOR LUW / DB2FORLUW / 970 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7.0.9.                              * 
****************************************************************

Do not use the "allow write access" reorg option

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

The problem is first fixed in DB2 version 9.7.0.9.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC95753 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

26.08.2013
17.12.2013
30.09.2015

9.7.0.9