|
Problem IC65946
|
Status: Closed |
INDEX_TBSPACEID OF SYSCAT.DATAPARTITIONS IS SET TO 0 FOR RANGE PARTITIONED TABLES WHEN UPGRADING FROM V9.1 OR V9.5 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
As an example, the following shows INDEX_TBSPACEID is 0 after
upgrading to V9.7.
$ db2 "select
substr(DATAPARTITIONNAME,1,12),DATAPARTITIONID,TBSPACEID,PARTITI
ONOBJECTID,INDEX_TBSPACEID from SYSCAT.DATAPARTITIONS where
TABNAME='T1'"
1 DATAPARTITIONID TBSPACEID PARTITIONOBJECTID
INDEX_TBSPACEID
------------ --------------- ----------- -----------------
---------------
PART0 0 2 4
0
PART1 1 2 5
0
PART2 2 2 6
0
PART3 3 2 7
0
PART4 4 2 8
0
If using db2look to extract the DDL, it falsely indicates
indexes are in "SYSCATSPACE".
For example, the following is the output of db2look:
CREATE TABLE "INST1 "."T1" (
"C1" INTEGER ,
"C2" VARCHAR(255) )
INDEX IN "T1_I1" PARTITION BY RANGE("C1")
(PART "PART0" STARTING(1) IN "USERSPACE1" INDEX
IN "SYSCATSPACE",
PART "PART1" STARTING(201) IN "USERSPACE1"
INDEX IN "SYSCATSPACE",
PART "PART2" STARTING(401) IN "USERSPACE1"
INDEX IN "SYSCATSPACE",
PART "PART3" STARTING(601) IN "USERSPACE1"
INDEX IN "SYSCATSPACE",
PART "PART4" STARTING(801) ENDING(1000) IN
"USERSPACE1" INDEX IN "SYSCATSPACE");
This only happens on big-endian platforms like AIX. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* big-endian platforms like AIX *
****************************************************************
* PROBLEM DESCRIPTION: *
* INDEX_TBSPACEID of SYSCAT.DATAPARTITIONS is set to 0 for *
* range partitioned tables when upgrading from V9.1 or V9.5 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to version 9.7 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66915
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.01.2010
07.03.2011
07.03.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
