home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC84224 Status: Geschlossen

CANNOT SET EXCLUDE XML COLUMNS CLAUSE IN STATISTICS PROFILE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When running runstats 
on the command line with the Exclude XML Columns clause, it 
works 
perfectly.  However, when the stats profile is set with that 
clause, 
the stats profile ignores it and stores a runstats command for 
ALL 
columns and ALL indexes. 
 
ex: 
 
RUNSTATS ON TABLE sahana12.test2 with distribution on key 
columns and detailed indexes all excluding xml columns set 
profile 
DB20000I  The RUNSTATS command completed successfully. 
 
select substr(statistics_profile, 1, 150) as statistics_profile 
from syscat.tables where tabname='TEST2' 
 
STATISTICS_PROFILE 
---------------------------------------------------------------- 
------------------------------------ 
 
RUNSTATS ON TABLE "SAHANA12"."TEST2" ON ALL COLUMNS WITH 
DISTRIBUTION ON KEY COLUMNS AND DETAILED INDEXES ALL 
 
  1 record(s) selected. 
 
 
In the above we see that external statiscs_profile does not 
contain clause 'EXCLUDING XML COLUMN'. 
This problem is only with external statistics_profile storage, 
however when the command is executed runstats does not collect 
statistics on xml columns when 'excluding xml column' option is 
specified.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* software                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to version v101 fp1                                  * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
fixed in version v101 fp1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
04.12.2012
04.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList