IBM Support

IC82059: SPURIOUS PACKAGE CACHE OVERFLOWS REPORTED WHEN CACHE IS AT FULL UTILIZATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 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.
    

Local fix

Problem summary

  • ****************************************************************
    * 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                    *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IC82059

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-15

  • Closed date

    2012-06-12

  • Last modified date

    2012-06-12

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC84561

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 June 2012