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

ORACLE COMPATIBILITY MODE USES BLANK SENSITIVE COMPARISON FOR VARGRAPHIC
AND CAN LEAD TO WRONG RESULTS.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
In Oracle compatibility mode DB2 uses blank sensitive comparison 
for vargraphic data type and lead to wrong results. 
 
Conditions to hit this APAR: 
 
1. This APAR can be hit only on Oracle compatibility so the 
following registry variable should be set. 
    "DB2_COMPATIBILITY_VECTOR=ORA" 
2. Table column should have VARGRAPHIC data type. 
3. Index should be created on that column. 
4. In the query, WHERE clause should contain LIKE predicate. 
 
Example: 
 
db2 "create table t1(c1 vargraphic(5), c2 vargraphic(5))" 
DB20000I  The SQL command completed successfully. 
 
db2 "insert into t1 values('V','A'),('V1','AB')" 
DB20000I  The SQL command completed successfully. 
 
db2 "create index idx_t1 on t1(c1)" 
DB20000I  The SQL command completed successfully. 
 
db2 "select c1 from t1 where c1 like 'V%'" 
C1 
---------- 
V1 
 
  1 record(s) selected. 
 
Expected result: 
 
C1 
---------- 
V <-- Missing row 
V1 
  1 record(s) selected.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 Version 10.1 Fix pack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.11.2012
19.04.2013
19.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version