|
Problem IC66839
|
Status: Closed |
INSTANCE ABEND DUE TO STACK OVERFLOW WITH FUNCTION NOTPD_TRAVERSE__9SQLNQ_PIDFP9SQLNQ_OPRI |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During SQL/XQuery compilation, a query being compiled may cause
the DB2 instance to abend due to a stack overflow exception.
Although new behaviour in DB2 Version 9.5 should ideally cause
the DB2 agent to dump an sqlcode SQL0973N upon detecting such a
scenario, this may not happen when a very large predicate,
e.g., deeply nested series of NOTs, etc., is present in the
query. The stack trace from such an abend will look
like:
-------Frame------ ------Function + Offset------
0x0900000005740BEC
notpd_traverse__9sqlnq_pidFP9sqlnq_opriPbT3CP3loc + 0x14
0x090000000574164C
notpd_traverse__9sqlnq_pidFP9sqlnq_opriPbT3CP3loc + 0xA74
0x090000000574164C
notpd_traverse__9sqlnq_pidFP9sqlnq_opriPbT3CP3loc + 0xA74
0x090000000574164C
notpd_traverse__9sqlnq_pidFP9sqlnq_opriPbT3CP3loc + 0xA74
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* INSTANCE ABEND DUE TO STACK OVERFLOW WITH *
* FUNCTIONNOTPD_TRAVERSE__9SQLNQ_PIDFP9SQLNQ_OPRI *
****************************************************************
* PROBLEM DESCRIPTION: *
* INSTANCE ABEND DUE TO STACK OVERFLOW WITH *
* FUNCTIONNOTPD_TRAVERSE__9SQLNQ_PIDFP9SQLNQ_OPRIDuring *
* SQL/XQuery compilation, a query being compiled maycause the *
* DB2 instance to abend due to a stack overflowexception. *
* Although new behaviour in DB2 Version 9.7 shouldideally *
* cause the DB2 agent to dump an sqlcode SQL0973N *
* upondetecting such a scenario, this may not happen when a *
* verylarge predicate, e.g., deeply nested series of NOTs, *
* etc.,is present in the query. The stack trace from such an *
* abendwill looks like:-------Frame------ ------Function + *
* Offset------0x0900000005740BECnotpd_traverse__9sqlnq_pidFP9sql
* + *
* 0x140x090000000574164Cnotpd_traverse__9sqlnq_pidFP9sqlnq_opriP
* + *
* 0xA740x090000000574164Cnotpd_traverse__9sqlnq_pidFP9sqlnq_opri
* + *
* 0xA740x090000000574164Cnotpd_traverse__9sqlnq_pidFP9sqlnq_opri
* + 0xA74... *
****************************************************************
* RECOMMENDATION: *
* Customers running into this problem should upgrade to *
* DB2LUW version 9.7 fp3 *
**************************************************************** |
| Local Fix: |
In DB2 Version 9.5, users have the ability to control the size
of the runtime stack used by a DB2 agent.
Consequently,increasing the value for the "agent_stack_sz"
database configuration parameter will help workaround the
issue. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This APAR is fixed in DB2 LUW version 9.7 fp3 |
| Workaround |
In DB2 Version 9.7, users have the ability to control the size
of the runtime stack used by a DB2 agent.
Consequently,increasing the value for the "agent_stack_sz"
database configuration parameter will help workaround the
issue. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.03.2010
27.09.2010
27.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
