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

DB2 INSTANCE MAY ABEND in a OR predicate

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 Instance may abend in a statement with an OR predicate 
involving two columns to express a filter to qualify a condition 
like (col1=X and col2>Y) or (col1>X). 
 
The stack trace generated by this problem looks like 
 
<StackTrace> 
<![CDATA[ 
------RBP--------------RIP--------------ARGS-------------------- 
------------------------------------- 
<sqlnr_gen_twin_prd> 
<sqlnr_optprep> 
<sqlnr_optprep_action> 
<sqlnr_seq> 
<sqlnr_rcc> 
<sqlnr_exe> 
<sqlnn_cmpl> 
]]></StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 Instance may abend in a statement with an OR predicate   * 
*                                                              * 
* involving two columns to express a filter to qualify a       * 
* conditionlike (col1=X and col2>Y) or (col1>X).               * 
*                                                              * 
*   The stack trace generated by this problem looks like       * 
*                                                              * 
*   <StackTrace>                                               * 
*   <![CDATA[                                                  * 
*                                                              * 
* ------RBP--------------RIP--------------ARGS------------------ 
* --------------------------------------                       * 
*  <sqlnr_gen_twin_prd>                                        * 
*  <sqlnr_optprep>                                             * 
*  <sqlnr_optprep_action>                                      * 
*  <sqlnr_seq>                                                 * 
*  <sqlnr_rcc>                                                 * 
*  <sqlnr_exe>                                                 * 
*  <sqlnn_cmpl>                                                * 
*  ]]></StackTrace>                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 1.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem is found in DB2 Version 9.7 GA.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
18.01.2010
18.01.2010
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList