home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC70337 Status: Closed

INSTANCE ABEND DUE TO STACK OVERFLOW WITH FUNCTION
NOTPD_TRAVERSE__9SQLNQ_PIDFP9SQLNQ_OPRI

product:
DB2 FOR LUW / DB2FORLUW / 980 - 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:                                              * 
* Users compiling SQL/XQuery.                                  * 
**************************************************************** 
* 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 behavior 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    * 
* ...                                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Customer should upgrade to DB2 LUW (PureScale) version 9.8   * 
* fispack 4.                                                   * 
****************************************************************
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.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
This APAR is fixed in v9.8 fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.08.2010
03.08.2011
03.08.2011
Problem solved at the following versions (IBM BugInfos)
9.8.,
9.8.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.4 FixList