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 IT10131 Status: Geschlossen

SYSCAT.COLUMNS.NUMNULLS STATISTICS MIGHT BE ZERO WHEN "EXCLUDE NULL
KEYS" INDEX IS EMPTY

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The NUMNULLS statistics might be zero for columns that has an 
empty "EXCLUDE NULL KEYS" index. 
 
Conditions to hit this issue are : 
(1) the column is the leading column of an "EXCLUDE NULL KEYS" 
index and 
(2) the "EXCLUDE NULL KEYS" index is empty (i.e. all values are 
null) 
 
Note : Both conditions must present in order for the issue to 
occur, not only one of them.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First Fixed in DB2 10.5 Fix Pack 7                           * 
****************************************************************
Local-Fix:
Manually update the statistics. You can use below query : 
db2 "update sysstat.columns set NUMNULLS=<expected_num_nulls> 
where colname='<column_name>' and tabname='<table_name>' and 
tabschema='<schema_name>'"
Lösung
First Fixed in DB2 10.5 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.07.2015
09.05.2017
09.05.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList