|
Problem IC87877
|
Status: Closed |
ORACLE COMPATIBILITY MODE USES BLANK SENSITIVE COMPARISON FOR VARGRAPHIC AND CAN LEAD TO WRONG RESULTS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10 Fix pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
04.04.2013
04.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
