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

DB2 QUERY COMPILER CAN TRAP WHEN STMTHEAP is AUTOMATIC AND MEMORY is
CONSTRAINED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When STMTHEAP is automatic and memory is constrained, a memory 
allocation request to STMTHEAP can fail; but the next allocation 
request can succeed. The query compiler can fail to handle such 
a situation. When the problem is encountered, you can observe 
traps. 
 
An example trap is below 
 
sqlno_greedy_resume_part 
sqlno_greedy_next_part 
sqlno_crule_join 
sqlno_gen_partitions_for_QTB 
sqlno_plan_end_opr 
sqlno_each_opr 
sqlno_walk_qun 
sqlno_each_opr
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fix pack 1.                  * 
****************************************************************
Local Fix:
The following can help to reduce the possibility of encountering 
the problem: 
 
1) set STMTHEAP to a fixed value 
2) allow room for STMTHEAP to grow by increasing APPL_MEMORY and 
INSTANCE_MEMORY
Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.05.2012
05.11.2012
05.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)