home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC82594 Status: Closed

DB2 MIGHT ABEND WHEN EXECUTING A QUERY WITH NESTED OR PREDICATE

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Under rare scenarios, DB2 might abend under the following 
scenarios. 
1. The query has a nested OR predicate 
2. The deepest OR subterm has atleast one always false 
predicate. 
   Always false predicates are ones which can be found to be 
never true. eg. 1 = 0, col1 <> col1 (assuming col1 is not null), 
etc. 
3. The deep OR subterm has atleast one AND subterm. 
 
The following stack trace is observed: 
sqlnr_theorem_prover_detail 
sqlnr_prove_OR_tree 
sqlnr_theorem_prover 
sqlnr_qrwprep_phase2 
sqlnr_prep2_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_exe 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 version 950 fixpack 10                 * 
****************************************************************
Local Fix:
Rewrite the predicate to make the deep OR subterm be the last 
subterm in the topmost OR.
Solution
Problem is first fixed in DB2 version 950 fixpack 10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.04.2012
30.10.2012
30.10.2012
Problem solved at the following versions (IBM BugInfos)
9.5.0
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList