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 IC73682 Status: Closed

ADMIN_MOVE_TABLE CAN FAIL ON RANGE PARTITIONED TABLES WITH EXPLICITLY
DEFINED RANGE TABLESPACES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The problem only happens if ADMIN_MOVE_TABLE is creating the 
target table and we're trying to move a table from one 
tablespace to another. . It can be hit if ADMIN_MOVE_TABLE is 
called on a table where the tablespace for each range has been 
explicitly defined. For such a definition see below: 
 
   CREATE TABLE SALES 
   (SID     INTEGER, 
    AMOUNT  INTEGER)  INDEX IN TBSPX 
   PARTITION BY RANGE (SID NULLS LAST) 
   (STARTING FROM 1 INCLUSIVE ENDING AT 100 INCLUSIVE 
    IN TBSP11 INDEX IN TBSP21, 
    STARTING FROM 101 INCLUSIVE ENDING AT 200 INCLUSIVE 
    IN TBSP12 INDEX IN TBSP22) 
 
ADMIN_MOVE_TABLE will try to create the ranges in the old 
tablespace instead of the new one and fail with: 
 
SQL1754N  The index table space or long table space is not in 
the same database partition group as the primary table space. 
SQLSTATE=42838
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Callers of ADMIN_MOVE_TABLE on Range Partitioned Tables      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP4 or later.                            * 
****************************************************************
Local Fix:
Create target table before the move and instruct 
ADMIN_MOVE_TABLE to use that table for the move instead of 
creating its own.
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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
Fixed in DB2 V9.7 FP4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.01.2011
28.04.2011
28.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList