DB2 FOR LUW / DB2FORLUW / 950 - DB2

On HP IPF you might encounter trap due to stack exhaustion when 
compiling a query with many OR predicates. 
 
The stack of the failing agent may look like following: 
 
<StackTrace> 
ossDumpStackTrace 
OSSTrapFile4dumpEmiP9__siginfoPv 
sqlo_trce 
sqloEDUCodeTrapHandler 
sqlno_pred_classify 
sqlno_analyze_ANDORNOT 
sqlno_analyze_pred_expr 
</StackTrace> 
 
 
To prevent stack corruption due to to many levels of recursion 
DB2 checks for remaining stack memory before entering the next 
level of recursion. 
 
The current implementation of this check does report more free 
stack space memory than actually available on HP IPF. 
This prevents the DB2 Optimizer from detecting the stack memory 
exhaustion on time. 
 
The APAR will adress the stack memory check implementation on HP 
IPF.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on HP-UX platform.                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9.                       * 
****************************************************************

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 9.5 Fix Pack 9.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC77389 IC84149 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.06.2011
14.03.2012
14.03.2012

9.5.FP9