DB2 might crash during query compilation.
The problem can occur if we plan a ZZJN and the output
cardinality of the ZZJN has a provable maximum 1 or 0.
In the database log one can find the stack similar to the one
below
2016-09-21-11.44.11.852427-240 E397706E2848 LEVEL: Info
(Origin)
PID : 26197 TID : 47142626388288 PROC :
db2sysc
INSTANCE: szamraj NODE : 000 DB :
DAZFP1
APPHDL : 0-18 APPID:
*LOCAL.szamraj.160921154155
AUTHID : SZAMRAJ HOSTNAME: hotel54
EDUID : 18 EDUNAME: db2agent (DAZFP1)
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
true
DATA #3 : Boolean, 1 bytes
false
DATA #4 : Boolean, 1 bytes
false
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: 41
sqlerrmc: Order property truncated to zero columns.
sqlerrp : SQLNO146
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0xFFFFFF9C (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, 1000 bytes
SELECT COL1, COL2, ......
DATA #10: String, 473 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[210]
sqlno_crule_save_plans[100]
sqlno_crule_save_plans[720]
sqlno_order_chop_prop[100] |
