IBM Support

IC84260: DEACTIVATION WITH LARGE BUFFERPOOL MEMORY TAKES EXCESSIVELY LONG ON LARGE WINDOWS SYSTEM

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Deactivating a database with large bufferpool memory on Windows
    takes excessively long.  For example, it takes 10+ minutes to
    deactivate a database with 100GB of bufferpool memory.
    
    A workaround is to increase the units of memory allocation used
    for bufferpools from the default 128K to the maximum of 256MB:
    
      db2set DB2_ALLOCATION_SIZE=256M
    
    This requires stopping/starting the instance to take effect.
    
    This setting is an appropriate workaround for the size of
    systems vulnerable to this problem.  While DB2_ALLOCATION_SIZE
    is a deprecated registry variable, it is still effective in DB2
    Version 9.7.  Note that bufferpools will only use the amount of
    memory that is required, i.e. the full 256MB will not be used
    when only a portion of that amount is needed.
    
    The same symptom could be seen for any activity (eg. last
    connection out) which is driving database deactivation.
    

Local fix

  • db2set DB2_ALLOCATION_SIZE=256M
    ( requires stopping/starting the instance )
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Large Windows systems                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 10.1 Fix Pack 1                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 10.1 Fix Pack 1
    

Temporary fix

  • See Local Fix
    

Comments

APAR Information

  • APAR number

    IC84260

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-13

  • Closed date

    2012-11-02

  • Last modified date

    2012-11-02

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

    IC79337

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

Modules/Macros

  • sqo
    

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 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":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 November 2012