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 IT18479 Status: Closed

DB2 MAY RETURN INCORRECT RESULTS IF USING A CASE STATEMENT TO COMPARE
FIXED CHAR/GRAPHIC STRINGS IN VARCHAR2 COMPATIBILITY MODE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When comparing fixed character or graphic strings where either
side uses a CASE statement, DB2 may return incorrect results in
VARCHAR2 compatibility mode.

Example:

CREATE TABLE T(C1 CHAR(4))
INSERT INTO T VALUES ('M')
SELECT * FROM T WHERE C1 = CASE WHEN 1=1 THEN 'M' END

Incorrect Result:

C1
----

  0 record(s) selected.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description. The issue will be fixed in v10.1fp6,  *
* 10.5fp9 and later.                                           *
****************************************************************
* RECOMMENDATION:                                              *
* See Error Description. The issue will be fixed in v10.1fp6,  *
* 10.5fp9 and later. Please, check sysroute apars to see where *
* the issue is fixed.                                          *
****************************************************************
Local Fix:
From the example above, cast the CASE statement to a fixed
character string of the desired length:

SELECT * FROM T WHERE C1 = CAST((CASE WHEN 1=1 THEN 'M' END) AS
CHAR(1))

C1
--------
M

  1 record(s) selected.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT18343 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.12.2016
31.07.2017
31.07.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)