|
Problem IT34787
|
Status: Closed |
MON_UOW_EXECLIST CONSUMES MONHEAP EVEN WHEN OFF
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When the MON_UOW_EXECLIST database configuration parameter is
set to OFF every Db2 application will still consume monitor heap
relating to Executable ID list collection. This could result in
other processing failing to get monitor heap. This in turn
could lead to a FODC_Memory diagnostic collection. Here is a
sample stack that shows other processing failing to get monitor
heap:
fd_select
sqloReadNamedPipe
sqloReadVendorRC
sqloInvokeVendorFunction
pdVendorCallWrapper
pdInvokeCalloutScriptViaVendorAPI
dumpOnOOM
sqloMemLogPoolConditions
sqloGetMemoryBlockExtended
GetFastWriterRecord
collectRequestorActivities
collectLockEvent
sqlplWaitOnWP
sqlplMakeNewRequestNonSD
sqlplrq
sqliLockUncond
sqliLockForReadUncond
sqli_proc_leaf
sqlischf
sqlirdk
sqldIndexFetch
sqldRowFetch
sqlriFetch |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.6 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.6 or higher *
**************************************************************** |
| Comment |
Upgrade to Db2 11.1.4.6 or higher |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2020
31.03.2021
31.03.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
