|
Problem IC76645
|
Status: Closed |
ACTION INVOLVING DROPPING A TYPE USED BY A SELF-REFERENCING PROCEDURE MAY FAIL REPORTING AGENT_STACK_SZ IS TOO SMALL |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When dropping a TYPE, either implicitly or explicitly via DDL
operation, if the type is referenced by a procedure that calls
itself, we may enter an infinite loop and eventually fail.
The agent performing the operation will trap. The db2diag.log
may contain a message such as the following, indicating that the
AGENT_STACK_SZ is too small:
2011-03-04-18.24.58.610506+180 E2697181E626 LEVEL: Severe
PID : 29522 TID : 47745414981952PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-20 APPID:
*LOCAL.db2inst1.110304145957
AUTHID : DB2INST1
EDUID : 38 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:1000
MESSAGE : ADM0502C The DB2 instance has terminated abnormally.
To remedy this problem, increase the AGENT_STACK_SZ DBM
configuration
parameter. Contact IBM Support for further assistance.
The trap file may contain a stack with the following functions,
where sqlrldyf and sqlrldyf2 are called repeatedly:
0x00002B6C88E67C07 ossDumpStackTraceEx + 0x01ef
0x00002B6C88E629CE _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00cc
0x00002B6C8615105B sqlo_trce + 0x03fb
0x00002B6C861970A0 sqloEDUCodeTrapHandler + 0x0266
0x000000327980EB10 __pthread_mutex_cond_lock + 0x03c0
0x00002B6C86E98DE4
_ZN13SQLO_MEM_POOL19allocateMemoryBlockEmmmjmPPvPP17SqloChunkSub
groupPP12SMemLostNodeP12SMemLogEvent
+ 0x029e
0x00002B6C86E96932 sqlogmblkEx + 0x04f2
0x00002B6C849CC0E9 sqlmoAllocBlock + 0x007b
0x00002B6C86E96570 sqlogmblkEx + 0x0130
0x00002B6C86E4DE9F
_Z12sqldScanOpenP8sqeAgentP14SQLD_SCANINFO1P14SQLD_SCANINFO2PPv
+ 0x1d6b
0x00002B6C84E2E335 _ZN16sqlrlCatalogScan4openEv + 0x0367
0x00002B6C84E2DF79 _ZN16sqlrlCatalogScan11fetchOneRowEv +
0x0061
0x00002B6C84E29CC4
_Z19sqlrl_fetch_one_rowP8sqlrr_cbiP10sqlrl_fldsiS2_iiP8SQLZ_RID
+ 0x018c
0x00002B6C866C788E
_Z9sqlrldyf2P8sqlrr_cbPhsS1_sS1_sihS1_sS1_siibbRb + 0x034c
0x00002B6C866C736B
_Z8sqlrldyfP8sqlrr_cbPhsS1_sS1_sihS1_sS1_siibbbRb + 0x0b27
0x00002B6C866C795C
_Z9sqlrldyf2P8sqlrr_cbPhsS1_sS1_sihS1_sS1_siibbRb + 0x041a
0x00002B6C866C736B
_Z8sqlrldyfP8sqlrr_cbPhsS1_sS1_sihS1_sS1_siibbbRb + 0x0b27
0x00002B6C866C795C
_Z9sqlrldyf2P8sqlrr_cbPhsS1_sS1_sihS1_sS1_siibbRb + 0x041a
0x00002B6C866C736B
_Z8sqlrldyfP8sqlrr_cbPhsS1_sS1_sihS1_sS1_siibbbRb + 0x0b27 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 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 Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.05.2011
23.12.2011
23.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
