|
Problem IC77389
|
Status: Closed |
TOO MANY OR PREDICATES LEAD TO STACK CORRUPTION ON HP IPF |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on HP IPF platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 6. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.07.2011
06.06.2012
06.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
