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

-901 WHILE COMPILING A STATEMENT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Under rare scenarios, DB2 can trap when compiling a SQL 
statement if the following conditions are true: 
1. The SQL statement has at least 2 joins. 
 
2. The SQL statement has an equality join predicate. Assume one 
of the columns that participate in the join predicate is T1.C1. 
and Table T1 has a generated column that is generated based on 
C1. 
 
3. The generated column is not referenced in the SQL statement 
 
Possible stack is: 
 
0x0900000006BB1068 
sqlnx_exp_get_qual_colname__FP3locP9sqlnq_qncPcPiT4 + 0xC 
0x0900000006B8F670 
sqlnx_exp_SORT_analyze__FP23sqlnx_exp_lolepop_parms + 0x7D4 
0x0900000006BAB520 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x648 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
... 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x0900000006BAF7A4 
sqlnx_exp_descend_predicate__FP23sqlnx_exp_lolepop_parmsP9sqlno_ 
prdP19sqlno_plan_operatorP20sqlno_qun2plan_arrayPP19sqlno_plan_o 
perator + 0x310 
0x0900000006BAECEC 
sqlnx_exp_process_predicates__FP23sqlnx_exp_lolepop_parmsiP19sql 
no_plan_operator9sqlno_setPcP20sqlno_qun2plan_arrayPP19sqlno_pla 
n_operatorN22 + 0x80 
0x0900000006B969FC 
sqlnx_exp_FILTER_post__FP23sqlnx_exp_lolepop_parms + 0x1C8 
0x0900000006BAC1C8 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x12F0 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x0900000006BABF6C 
sqlnx_exp_analyze_plan__FP23sqlnx_exp_lolepop_parms + 0x1094 
0x09000000083775DC sqlnx_explain_plan__FP9sqlnq_qur + 0x864 
0x0900000008376CBC sqlnx_explain_plan__FP9sqlnq_qur@glue764 + 
0x74 
0x090000000518D964 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x1B1C 
0x0900000008E237FC 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x40 
... 
 
The query fails with -901 and/leads to a trap.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
07.11.2012
07.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList