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

QUERY COMPILER INCORRECTLY RETURNS SQLCODE -101 WHEN IT SHOULD NOT.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Under rare conditions, the query compiler might return sqlcode 
-101 when it should not. 
 
A db2trc flw output shows one of the following functions 
sqlno_find_jp_hash_table or sqlno_do_insert_qpt in the call 
stack when function sqlno_alloc_aub receives return code 
SQLO_NOMEM_STMTH from the functions it calls. 
 
Starting with DB2 Version 9.5 Fix Pack 6 and DB2 Version 9.7 Fix 
Pack 3, confirmation of the problem can be made from db2 diaglog 
entries.   At DIAGLEVEL 3 or higher, the db2 diaglog file shows 
a compiler error stack for rc -2144272209 logged by sqlnn_cmpl. 
The error stack will contain one of the problematic functions 
sqlno_find_jp_hash_table or sqlno_do_insert_qpt.  The following 
is an example with sqlno_find_jp_hash_table in 
the error stack. 
 
2010-11-02-08.39.56.394386-300 E527827E1139   LEVEL: Info 
PID : 18633  TID : 47702863767872   PROC : db2sysc 0 
INSTANCE: myinst    NODE : 000      DB   : MYDB 
APPHDL  : 0-12838   APPID: 10.42.0.102.49829.101102125142 
AUTHID  : MYAUTHID 
EDUID   : 254                  EDUNAME: db2agent (MYDB) 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, 599 bytes 
Compiler error stack for rc = -2144272209: 
sqlnn_cmpl[390] 
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[900] 
sqlno_plan_end_opr[100] 
sqlno_gen_partitions_for_Q[400] 
sqlno_crule_join[100] 
sqlno_get_best_plan[100] 
sqlno_get_best_plan[200] 
sqlno_find_plan_chain[200] 
sqlno_find_plan_entry[120] 
sqlno_hash_PRDs[120] 
sqlno_jp_hash_N_word_key[100] 
sqlno_find_jp_hash_table[160] 
sqlno_insert_prd_set[100] 
sqlno_copy_setN[100] 
sqlno_grow_pool[200] 
sqlno_alc_aub[10] 
 
Starting with DB2 Version 9.5, STMTHEAP permitted an AUTOMATIC 
attribute.  This problem is independent of the AUTOMATIC 
attribute.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Under rare conditions, the query compiler might return       * 
* sqlcode  -101 when it should not.                            * 
*                                                              * 
* A db2trc flw output shows one of the following functions     * 
* sqlno_find_jp_hash_table or sqlno_do_insert_qpt in the call  * 
* stack when function sqlno_alloc_aub receives return code     * 
* SQLO_NOMEM_STMTH from the functions it calls.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users can upgrade to DB2 V9.5 fix pak 8 to avoid this        * 
* defect.                                                      * 
****************************************************************
Local Fix:
It is possible that a small increase in the STMTHEAP 
setting will allow the statement to compile without experiencing 
the -101 error.
Solution
First Fixed in DB2 Version V9.5 fix pak 8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73603 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.12.2010
05.07.2011
05.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.
Problem solved according to the fixlist(s) of the following version(s)