DB2 FOR LUW / DB2FORLUW / A10 - DB2

When the error is occurs, the db2diag.log will contain the 
following entry, and the stack trace contains the functions 
listed as "Compiler error 
stack" in this entry. 
 
2014-08-20-17.48.07.616025+540 E826772E1843          LEVEL: Info 
(Origin) 
PID     : 8763                 TID : 140339738306304 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
CUSTDB 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.140820084800 
AUTHID  : DB2INST1             HOSTNAME: DB2HOST 
EDUID   : 22                   EDUNAME: db2agent (CUSTDB) 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 
true 
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: 30 
 sqlerrmc: optBitFilterSize less than min 
 sqlerrp : SQLNG060 
 sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x000000A2      (5) 0xFFFFF8D7      (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, 144 bytes 
(SQL_statement_that_had_error) 
DATA #10: String, 330 bytes 
Compiler error stack for rc = -2144272209: 
sqlnn_cmpl[415] 
sqlng_main[3252] 
sqlng_main[1713] 
sqlng_build_thread[859] 
sqlngProcessLolepop[543] 
sqlng_process_return_op[1666] 
sqlngProcessLolepop[543] 
sqlng_process_pipe_op[881] 
sqlngProcessLolepop[543] 
sqlng_process_mate_op[1484] 
sqlngProcessLolepop[543] 
sqlng_process_hsjn_op[1833]

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.1 FixPack 5 or later.              * 
****************************************************************

Use optimizer guidelines to choose a join method other than hash 
join, or use query optimization class 3 not to pick up hash 
join. 
However, note that completely avoiding hash join in the entire 
instance could cause a severe performance degradation.

This problem was first fixed in DB2 V10.1 FixPack 5.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

18.09.2014
17.07.2015
17.07.2015