|
Problem IC63769
|
Status: Geschlossen |
INSTANCE CRASH DUE TO STACK OVERFLOW WITH FUNCTION SQLNG_PROCESS_BF_NODE OR SQLNG_PROCESS_PARSE_TREE_NODE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
During SQL compilation, a query being compiled may cause the DB2
instance to crash due to a stack overflow exception. However,
the new behaviour in DB2 Version 9.5 should ideally cause the
DB2 agent to return an sqlcode SQL0973N upon detecting such a
scenario.
The stack trace from such an abend will look like:
-------Frame------ ------Function + Offset------
0x0900000004C8FC94
sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid + 0x50
0x0900000004C9108C
sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid + 0x1448
0x0900000005AF8DB0
sqlng_process_BF_node__FP9sqlng_blkP9sqlnq_pid + 0x134
0x0900000004C9108C
sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid + 0x1448
0x0900000005AF8DB0
sqlng_process_BF_node__FP9sqlng_blkP9sqlnq_pid + 0x134
0x0900000004C9108C
sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid + 0x1448
0x0900000005AF8DB0
sqlng_process_BF_node__FP9sqlng_blkP9sqlnq_pid + 0x134
*
* The function sqlng_process_parse_tree_node() and
sqlng_process_BF_node is repeated many times
*
0x0900000004C9108C
sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid + 0x1448
0x0900000005AF8DB0
sqlng_process_BF_node__FP9sqlng_blkP9sqlnq_pid + 0x134
0x0900000004C9108C
sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid + 0x1448
0x0900000005AF8DB0
sqlng_process_BF_node__FP9sqlng_blkP9sqlnq_pid + 0x134
.... |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Users who issue a complex query causing stack overflowduring *
* compiling. *
****************************************************************
* PROBLEM DESCRIPTION: *
* During SQL compilation, a query being compiled may cause *
* theDB2instance to crash due to a stack overflow *
* exception.However,the new behaviour in DB2 Version 9.5 *
* should ideally causetheDB2 agent to return an sqlcode *
* SQL0973N upon detecting suchascenario.The stack trace from *
* such an abend will look like:-------Frame------ *
* ------Function + *
* Offset------0x0900000004C8FC94sqlng_process_parse_tree_node__F
* +0x500x0900000004C9108Csqlng_process_parse_tree_node__FP9sqlng
* +0x14480x0900000005AF8DB0sqlng_process_BF_node__FP9sqlng_blkP9
* + *
* 0x1340x0900000004C9108Csqlng_process_parse_tree_node__FP9sqlng
* +0x14480x0900000005AF8DB0sqlng_process_BF_node__FP9sqlng_blkP9
* + *
* 0x1340x0900000004C9108Csqlng_process_parse_tree_node__FP9sqlng
* +0x14480x0900000005AF8DB0sqlng_process_BF_node__FP9sqlng_blkP9
* + 0x134** The function sqlng_process_parse_tree_node() *
* andsqlng_process_BF_node is repeated many *
* times*0x0900000004C9108Csqlng_process_parse_tree_node__FP9sqln
* +0x14480x0900000005AF8DB0sqlng_process_BF_node__FP9sqlng_blkP9
* + *
* 0x1340x0900000004C9108Csqlng_process_parse_tree_node__FP9sqlng
* +0x14480x0900000005AF8DB0sqlng_process_BF_node__FP9sqlng_blkP9
* + 0x134.... *
****************************************************************
* RECOMMENDATION: *
* In DB2 Version 9.5, users have the ability to control *
* thesize of the runtime stack used by a DB2 *
* agent.Consequently,increasing the value for the *
* "agent_stack_sz"database configuration parameter will help *
* workaround theissue. *
**************************************************************** |
| 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. |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in Version 9.5 Fix pack6 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC64116
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 15.10.2009
31.05.2010
31.05.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.
|
| Problem behoben lt. FixList in der Version |
