DB2 - Problembeschreibung
| Problem IC74234 | Status: Geschlossen |
DB2LOOK MAY GENERATE WRONG INDEX STATEMENT WITH THE "PARTITIONED" CLAUSE EVEN WHEN THE INDEX WAS CREATED WITH "NON PARTITIONED" | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problembeschreibung: | |
db2look may generate wrong CREATE INDEX statement with the
"PARTITIONED" clause even when the index was originally created
with
the "NON PARTITIONED" clause, for example:
CREATE INDEX "FAP"."I03" ON
"FAP"."T1" (STARTDATUM" ASC, "KUNDE" ASC)
NOT PARTITIONED COMPRESS YES ALLOW REVERSE SCANS;
db2look output:
CREATE INDEX "FAP "."I03" ON "FAP"."T1"
("STARTDATUM" ASC,
"KUNDE" ASC)
PARTITIONED <<<< wrong
COMPRESS YES ALLOW REVERSE SCANS;
This problem can only occur if you use the same index name in at
least two different database schema's. And in one of these
schema's the
index was created as "PARTITIONED", where as in the other it was
created
as "NOT PARTITIONED".
For this index db2look will generate a wrong index statement
with
the "PARTITIONED" clause. | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * pgrade to DB2 Version 9.7 Fix Pack 5. * **************************************************************** | |
| Local-Fix: | |
| verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
| Lösung | |
First fixed in Version 9.7 Fix Pack 5. | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.02.2011 20.12.2011 20.12.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
| Problem behoben lt. FixList in der Version | |
| 9.7.0.5 |
|