DB2 - Problem description
| Problem IC74573 | Status: Closed |
DB2LOOK, WHEN EXECUTED WITH BOTH -T AND -L, DOES NOT GENERATE THE DDL FOR TABLESPACES OF PARTITIONED INDEXES | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
If db2look is executed with both -t and -l, for a range
partitioned table, then the create tablespace DDLs are not
generated for the partitioned indexes.
For example, given the following table definition in database
SAMPLE:
CREATE TABLE "DB2INST1"."TEST" (
"COL1" INTEGER ,
"COL2" INTEGER )
PARTITION BY RANGE("COL1")
(PART "0" STARTING(0) ENDING(10) IN "USERSPACE1" INDEX IN
"TESTSPACE");
db2look -d SAMPLE -t TEST -e -l will not generate the create
tablespace DDL for TESTSPACE, even though it's a user-defined
tablespace.
However, if db2look is executed with -l and WITHOUT -t
<tablename>, then the DDL for tablespaces of partitioned indexes
will be generated. db2look should provide the partitioned index
tablespace DDL when -t and -l are used together. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * If db2look is executed with both -t and -l, for a range * * partitioned table, then the create tablespace DDLs are not * * generated for the partitioned indexes. * **************************************************************** * RECOMMENDATION: * * Update to Version 9.7 Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
Run db2look with -l but without the -t <tablename> filter to get the tablespace DDL for the partitioned indexes | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
| Solution | |
Problem was 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 : | 18.02.2011 17.01.2012 17.01.2012 |
| 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 |
|