DB2 FOR LUW / DB2FORLUW / 970 - DB2

When the registry variable DB2_COMPATIBILITY_VECTOR=ORA is set 
for the instance, running the SQL statement 
 
REORG INDEXES ALL FOR TABLE <Schema_name.Table_name> ON DATA 
PARTITION <partition_id> 
 
on a range partitioned table may fail with 
 
SQL2222N  The specified data partition "<partition_id>" is not 
valid. Reason code: "3" . 
 
This error is expected when the data partition is not in normal 
status, but is not expected when the data partition is visible. 
The following query can be used to determine if the partition is 
in normal (visible) status: 
 
SELECT datapartitionname, datapartitionid, status FROM 
syscat.datapartitions WHERE tabschema = <Schema_name> and 
tabname = <Table_name> 
 
If the STATUS column shows a blank, then the partition is in 
normal status and the REORG command should have been successful. 
 If the STATUS column shows a value of A, D, L, or I, then the 
reorg cannot run on that partition.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description Above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix pack 5.                       * 
****************************************************************

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

First Fixed in Version 9.7 Fix Pack 5.

keiner bekannt / siehe Local-Fix

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

24.02.2011
19.12.2011
19.12.2011

9.7.FP5