home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC74683 Status: Closed

REORG INDEXES ALL AGAINST A PARTITIONED TABLE WITH THE ON DATA PARTITION
CLAUSE MAY FAIL WITH SQL2222N RC 3

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description Above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix pack 5.                       * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
First Fixed in Version 9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.02.2011
19.12.2011
19.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList