With the Statement Monitor switch is on, the following
"Package Cache Overflow" message in the db2diag.log may be seen
many times:
xxxx-xx-xx-xx.xx.xx.xxxxxx+xxx xxxxxxxxxxxxxx LEVEL: Event
PID : xxxxxxx TID : xxxxx PROC : db2sysc
0
INSTANCE: db2 NODE : 000 DB : SAMPLE
APPHDL : 0-xxxxx APPID:
xx.xxx.xxx.xx.xxxxx.xxxxxxxxxxx
AUTHID : xxxxxxxx
EDUID : xxxxx EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, access plan manager, sqlra_cache_mem_please,
probe:100
MESSAGE : ADM4500W A package cache overflow condition has
occurred. There is
no error but this indicates that the package cache has
exceeded the
configured maximum size. If this condition persists,
you should
perform additional monitoring to determine if you need
to change the
PCKCACHESZ DB configuration parameter. You could also
set it to
AUTOMATIC.
REPORT : APM : Package Cache : info
IMPACT : Unlikely
DATA #1 : String, 274 bytes
Package Cache Overflow
memory needed : 753
current used size (OSS) : 15984666
maximum cache size (APM) : 15892480
maximum logical size (OSS): 40164894
maximum used size (OSS) : 48562176
owned size (OSS) : 26017792
number of overflows : xxxxx
these may be followed by corresponding
"Package Cache Overflow #xxxxx Resolved" messages.
At some point the Package Cache Overflow state may persist
(i.e. a "Package Cache Overflow" without a following
"Package Cache Overflow Resolved" message).
When the package cache overflows and particularly if the
overflow state persists, then performance can degrade
significantly and out of memory errors can occur. |
