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

DB2 MIGHT PRODUCE SQL0901N ERROR WHEN EXECUTING QUERY WITH PREDICATES WITH
TIMESTAMP DURATIONS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 might produce SQL0901N if the following conditions are true: 
1) The query consists of a predicate of form TIMESTAMP <relop> 
TIMESTAMP 
2) <relop> can refer to any relational operator such as =, <>, 
>, < , etc 
3) Either sides of the predicate is either column or constant 
of type TIMESTAMP or is a function which returns a datatype of 
TIMESTAMP 
4) At least one side of the predicate references some form of 
time duration arithmetic operation 
 
eg. 
select * from T1 
where TScol + current timezone = timestamp(DATE(current timezone 
+ TScol), current_time); 
 
Will generate stack similar to this: 
 
0        ossDumpStackTraceInternal 
1        ossDumpStackTraceV98 
2        OSSTrapFile::dumpEx 
3        sqlo_trce 
4        sqloDumpDiagInfoHandler 
5        __restore_rt 
6        pthread_kill 
7        ossPthreadKill 
8        sqloDumpEDU 
9        sqldDumpContext 
10       sqlrr_dump_ffdc 
11       sqlzeDumpFFDC 
12       sqlzeMapZrc 
13       sqlrrMapZrc 
14       sqlritme 
15       sqlriExecThread 
16       sqlriSectInvoke 
17       sqlriExecOpenThread 
18       sqlrr_process_open_request
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* UNKNOWN                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 101 fix pack 5                        * 
****************************************************************
Local Fix:
Solution
The problem was first fixed in DB2 version 101 fix pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.03.2015
12.08.2015
12.08.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList