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

SELECT DISTINCT WITH LANGUAGE AWARE COLLATION SEQUENCE WITH EO S1
ATTRIBUTE MAY RETURN WRONG RESULTS

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
In a unicode database which was created with a language aware 
collation sequence, like "UCA500R1_LROOT_AN_CX_EO_FX_HX_NX_S1" 
a SELECT DISTINCT may return wrong results. 
 
The problem is that despite attributes "EO S1" are specified, 
which should respect case sensitivity, a string may be sorted as 
a duplicate and therefore may be missing from the result set. 
 
This problem happens only if the case difference is after the 
7th character. 
 
For example suppose 5 rows containing the column values: 
 
Achter de Hoven 
Achter de Hoven 
Achter De Hoven 
Achter de Hoven 
Achter de Hovenstraat 
 
Then a "select distinct(column) ..." returns just: 
 
Achter de Hoven 
Achter de Hovenstraat 
 
which is wrong because "Achter De Hoven" is missing. The case 
sensitivity was not respected.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In a unicode database which was created with a language      * 
* aware collation sequence, like                               * 
* "UCA500R1_LROOT_AN_CX_EO_FX_HX_NX_S1"                        * 
* a SELECT DISTINCT may return wrong results.                  * 
*                                                              * 
* The problem is that despite attributes "EO S1" are           * 
* specified, which should respect case sensitivity, a string   * 
* may be                                                       * 
* sorted as a duplicate and therefore may be missing from the  * 
* result                                                       * 
* set.                                                         * 
*                                                              * 
* This problem happens only if the case difference is after    * 
* the 7th character.                                           * 
*                                                              * 
* For example suppose 5 rows containing the column values:     * 
*                                                              * 
* Achter de Hoven                                              * 
*                                                              * 
* Achter de Hoven                                              * 
*                                                              * 
* Achter De Hoven                                              * 
*                                                              * 
* Achter de Hoven                                              * 
*                                                              * 
* Achter de Hovenstraat                                        * 
*                                                              * 
*                                                              * 
*                                                              * 
* Then a "select distinct(column) ..." returns just:           * 
*                                                              * 
* Achter de Hoven                                              * 
*                                                              * 
* Achter de Hovenstraat                                        * 
*                                                              * 
* which is wrong because "Achter De Hoven" is missing. The     * 
* case sensitivity was not respected.                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.5 FixPak 6                      * 
****************************************************************
Local-Fix:
Either: 
 
Creating an index on the column allows select distinct to return 
the correct result. Verify that optimizer chooses the index. 
 
Or: 
 
Avoid a BINSORT used by DB2 internally by setting registry 
variable: 
 
db2set DB2_BINSORT=off
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 UDB Version 9.5 FixPak 6
Workaround
see LOCAL FIX.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC63837 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.10.2009
01.09.2010
01.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version