suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT21985 Status: Closed

DOING LIKE ON A CODEUNITES32 FIXED LENGTH COLUMN  IN THE COLUMNAR
ORGANIZED TABLE COULD RETURN AN INCORRECT RESULT

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Example: 
CREATE TABLE TEST_ROW (TEST CHAR(2 CODEUNITS32)) organize by row 
 
INSERT INTO TEST_ROW VALUES ('AE') 
select * from  TEST_ROW WHERE  TEST LIKE 'AE' 
TEST 
-------- 
AE 
 
 
CREATE TABLE TEST_CDE (TEST CHAR(2 CODEUNITS32)) organize by 
column 
INSERT INTO TEST_CDE VALUES ('AE') 
select * from  TEST_CDE WHERE  TEST LIKE '%AE' 
TEST 
-------- 
 
  0 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CODEUNITES32 FIXED LENGTH COLUMNS                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please See Error Description and install fix.                * 
****************************************************************
Local Fix:
avoid using CODEUNITS32 FIXED LENGTH COLUMNS
available fix packs:
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Please See Error Description and install fix.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.08.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)