DB2 - Problem description
Problem IC80868 | Status: Closed |
DECODE FUNCTION MAY NOT MATCH NULL VALUES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When the first parameter of the DECODE function is a string type, it may not match a NULL value at an even number position of the DECODE function. This also applies to '' (empty string) when database is in ORA mode. Example: select decode (a1, null, 'null', '00') as a1 from (select cast (NULL as CHAR) as a1 from table (values(1))); returns '00' instead of 'null'. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * When using 'DB2_COMPATIBILITY_VECTOR=ORA' * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2_v97fp6 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84304 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.01.2012 09.04.2014 09.04.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |