DB2 FOR LUW / DB2FORLUW / 970 - DB2

When issuing a pause on an inplace table reorg that has nearly 
finished reorganizing the table, DB2 may incorrectly return 
SQL2219N Reason Code 11: "There is no table reorganization to 
PAUSE or STOP". However, monitoring utilities may still show 
that the reorganization is still in progress. This contradiction 
occurs during a timing window where the reorganization has 
completed processing all rows but has not yet committed because 
it is waiting for existing readers and writers on the table to 
complete.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An SQL2219N RC=11 error may be returned stating that there   * 
* is no reorg on the table even though monitoring shows that   * 
* there is a reorg on the table. This reorg has finished       * 
* moving rows, but has not yet fully committed.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 6.                              * 
****************************************************************

The reorg on the table has completed processing and is waiting 
for 
existing readers and writers to complete. The SQL2219N RC=11 
error message may be safely ignored. The reorg will commit and 
disappear from monitoring when all existing readers and writers 
complete.

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 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
 

This problem was first fixed in DB2 V9.7 Fix Pack 6. Instead of 
returning SQL2219N RC=11 in this scenario, DB2 will now return 
SQL2219N RC=10, which is a more accurate reflection of the 
correct status of the inplace reorg.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC81291 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.11.2011
04.07.2014
04.07.2014

9.7.FP6