DB2 - Problem description
Problem IC63207 | Status: Closed |
WRONG RESULTS WITH LIKE EXPRESSION USING '^' (CIRCUMFLEX ACCENT)AND LANGUAGE AWARE COLLATION SEQUENCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
In a unicode database which was created with a "language aware collation" sequence, like "UCA500R1_LROOT_AN_CX_EX_FX_HX_NX_S2" we may see wrong results with pattern matching during a expression using LIKE and the character "^" (CIRCUMFLEX ACCENT). For example the following query retruns wrong result: db2 select case when '^' like '^' then 1 else 0 end from sysibm.sysdummy1 1 ----------- 0 This does not happen with the default collating sequence (IDENTITY). | |
Problem Summary: | |
Users Affected: ALL Problem Description: In a unicode database which was created with a "language aware collation" sequence, like "UCA500R1_LROOT_AN_CX_EX_FX_HX_NX_S2" we may see wrong results with pattern matching during a expression using LIKE and the character "^" (CIRCUMFLEX ACCENT). For example the following query retruns wrong result: db2 select case when '^' like '^' then 1 else 0 end from sysibm.sysdummy1 1 ----------- 0 This does not happen with the default collating sequence (IDENTITY). Problem Summary: In a unicode database which was created with a "language aware collation" sequence, like "UCA500R1_LROOT_AN_CX_EX_FX_HX_NX_S2" we may see wrong results with pattern matching during a expression using LIKE and the character "^" (CIRCUMFLEX ACCENT). For example the following query retruns wrong result: db2 select case when '^' like '^' then 1 else 0 end from sysibm.sysdummy1 1 ----------- 0 This does not happen with the default collating sequence (IDENTITY). | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 UDB Version 9.5, FixPak 5 (build s091123) | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.09.2009 15.12.2009 16.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.5 |