|
Problem IC81291
|
Status: Closed |
PAUSING INPLACE TABLE REORG RETURNS SQL2219N RC=11, BUT OLR SHOWS AS IN PROGRESS |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* 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 the latest fix pack. *
**************************************************************** |
| Local Fix: |
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. |
| Solution |
This problem was first fixed in DB2 V9.5 Fix Pack 10. 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. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.02.2012
04.09.2012
04.09.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.10
|
 |
