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

USER MAY OBSERVE INCORRECT SCAN RESULT WHEN QUERYING GRAPHIC TYPE COLUMNS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Index Manager fails to properly initialize a structure that 
containing codepage member passed to the graphic keypart 
comparison routines. As a result trailing blanks in graphic 
strings are not treated as proper codepage data. This results in 
incorrect comparison which in turn causes incorrect index scan 
result. The query ends up not returning the rows containing the 
trailing blanks even tough they satisfy the query conditions. 
This only happens when the IDENTITY collating sequence is used.
Problem-Zusammenfassung:
Users who set IDENTITY collating sequence
Local-Fix:
Change the IDENTITY collating sequence to the others
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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

Lösung
Problem was first fixed in DB2 Version 9.7 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.12.2009
25.05.2010
18.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.,
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList