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

SQL0901/SQL0183 MIGHT OCCUR WHEN RUNNING QUERIES CONTAINING
CASESUB-EXPRESSIONS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
SQL0901 might occur when running queries containing the
following characteristics on column organized tables:

1. the select list contains at least one expression
2. the expression contains CASE sub-expresssion
3. the result data type of the CASE sub-expression is different
from the result data type of the expression

For non column organized table it may manifest as SQL0183 when
calling DATE function with CASE statement:

create table t1 (c1 timestamp not null);
select int(date(case when 1=1 then c1 end)) from t1;

1
-----------
SQL0183N  A datetime arithmetic operation or a datetime scalar
function has a
result that is not within the valid range of dates.
SQLSTATE=22008
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local Fix:
Work-around:
DB2COMPOPT=NO_SIMPL_CASE_HXP
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.04.2018
28.01.2020
28.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)