DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

Users Affected: ALL 
 
Problem Description: See Error Description. 
 
Problem Summary:  See Error Description.

Either: 
 
Creating an index on the column allows select distinct to return 
the correct result. 
 
Or: 
 
Avoid a BINSORT used by DB2 internally by setting registry 
variable: 
 
db2set DB2_BINSORT=off

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 UDB Version 9.7, FixPak 2 (build s100514)

see LOCAL FIX.

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

20.10.2009
09.06.2010
09.06.2010

9.7.