DB2 FOR LUW / DB2FORLUW / 970 - DB2

Spurious Package cache overflows might be reported due to timing 
conditions which falsely trigger DB2 to think it has exceeded 
the configured size. 
 
The current used size hardly exceeds the maximum cache size at 
the time the overflow is reported and the overflow is also 
reported to be resolved straight away. Example: 
 
With PCKCACHESZ set to 40000 
 
2012-03-15-02.10.29.770037+060 E39763621A1173     LEVEL: Event 
PID     : xxx             TID  : xxx     PROC : db2sysc 0 
INSTANCE: xxxx            NODE : 000         DB   : xxxx 
APPHDL  : xxx             APPID: xxxx 
AUTHID  : xxx 
EDUID   : xxx              EDUNAME: db2agent (xxx) 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, 277 bytes 
Package Cache Overflow 
memory needed             : 376 
current used size (OSS)   : 158924904 
maximum cache size (APM)  : 158924800 
maximum logical size (OSS): 159116039 
maximum used size (OSS)   : 178520064 
owned size (OSS)          : 178520064 
number of overflows       : 218 
 
2012-03-15-02.10.29.794177+060 E39764795A747      LEVEL: Event 
PID     : xxx              TID  : xxx       PROC : db2sysc 0 
INSTANCE: xxx            NODE : 000         DB   : xxxx 
APPHDL  : xxx             APPID: xxxx 
AUTHID  : xxxx 
EDUID   : xxx             EDUNAME: db2agent (xxx) 0 
FUNCTION: DB2 UDB, access plan manager, sqlra_cache_mem_please, 
probe:200 
REPORT  : APM : Package Cache : info 
IMPACT  : Unlikely 
DATA #1 : String, 260 bytes 
Package Cache Overflow #218 Resolved. 
memory needed             : 251 
current used size (OSS)   : 158906248 
maximum cache size (APM)  : 158924800 
maximum logical size (OSS): 159116039 
maximum used size (OSS)   : 178520064 
owned size (OSS)          : 178520064 
 
 
These messages are not a reason for alarm. 
 
1. The overflow is  resolved within the sub-second. So space 
remains in the cache overall. 
 
2. The percentage of the overflow is minimal so we are not in 
danger of being out allocatable memory. 
 
 
This APAR will avoid these kind of messages in the db2diag.log 
which are reporting a false alarm.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Additional checking has been introduced to avoid spurious    * 
* overflow messages.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 and Fix pack 6                    * 
****************************************************************

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
 

Problem was first fixed in DB2 version 9.7 and Fix Pack 6

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC84561 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.03.2012
12.06.2012
12.06.2012

9.7.