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

QUERY COMPILATION MAY FAIL WITH: -901 SQLNO_GET_BEST_PLAN[200] WHEN ZIGZAG
JOIN (ZZJN) IS CONSIDERED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A query compilation might fail with SQL0901N ( 
sqlno_get_best_plan) if a ZigZag join is considered. 
 
FODC_AppErr data is written and the following can be seen in 
db2diag.log: 
 
2015-03-02-12.38.45.394532+060 I142140A919          LEVEL: 
Severe 
PID     : 10354794             TID : 263679         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-25631              APPID: 
199.99.66.94.36392.150302113429 
AUTHID  : USER12               HOSTNAME: myhost 
EDUID   : 263679               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 58 
 sqlerrmc: sqlno_get_best_plan       [200]:rc(     0) 
 sqlerrp : SQLNN067 
 sqlerrd : (1) 0x803100AF      (2) 0x000000AF      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFDA8      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 
2015-03-02-12.38.53.068015+060 E202409A2288         LEVEL: Info 
(Origin) 
PID     : 10354794             TID : 263679         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-25631              APPID: 
199.99.66.94.36392.150302113429 
AUTHID  : USER12               HOSTNAME: myhost 
EDUID   : 263679               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 
MESSAGE : ZRC=0x803100AF=-2144272209=SQLNN_E_BADNEWS 
          "unexpected error but state is OK" 
DATA #1 : String, 62 bytes 
An unexpected error was detected during statement compilation. 
DATA #2 : Boolean, 1 bytes 
false 
DATA #3 : Boolean, 1 bytes 
false 
DATA #4 : Boolean, 1 bytes 
true 
DATA #5 : Boolean, 1 bytes 
false 
DATA #6 : Hex integer, 4 bytes 
0x00000000 
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 58 
 sqlerrmc: sqlno_get_best_plan       [200]:rc(     0) 
 sqlerrp : SQLNN067 
 sqlerrd : (1) 0x803100AF      (2) 0x000000AF      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFDA8      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #8 : Hex integer, 4 bytes 
0x00000040 
DATA #9 : String with size, 451 bytes 
SELECT ... 
DATA #10: String, 445 bytes 
Compiler error stack for rc = -2144272209: 
sqlnn_cmpl[380] 
sqlno_exe[900] 
sqlno_planning_phase[200] 
sqlno_planning_scan[400] 
sqlno_scan_utils_qgm[200] 
sqlno_each_qur[400] 
sqlno_top_qtb[100] 
sqlno_each_opr[200] 
sqlno_walk_qun[100] 
sqlno_each_opr[1200] 
sqlno_plan_end_opr[100] 
sqlno_gen_partitions_for_Q[300] 
sqlno_open_part[410] 
sqlno_generate_zzjn_plans[40] 
sqlno_generate_single_fact[80] 
sqlno_zzjn_generate_snowfl[10] 
sqlno_get_best_plan[200] 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local Fix:
disable ZigZag joins by setting the following keyword 
db2set DB2_REDUCED_OPTIMIZATION='ZZJN OFF'
Solution
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.03.2015
15.07.2015
15.07.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