IBM Support

IC73419: SLIGHT OVERLAP DURING DATABASE DEACTIVATION/REACTIVATION THAT MAY LEAD TO OLD/NEW DATABASE MEMORY ALLOCATED AT THE SAME TIME.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The current design of deactivation/activation of a database
    partition allows there to be a slight overlap where, at the
    point where shared memory is allocated for the "new" activation,
    shared memory from the previous activation has not yet been
    freed.  Note that all activity is completed for the old
    activation, it is just the shared memory itself that may not yet
    be freed.
    
    This may lead to diag.log messages such as the following which
    indicate that we are exhausting shared memory resources:
    
    
    2009-05-22-12.38.15.369802-240 I6841457A939       LEVEL: Warning
    
    PID     : 106946               TID  : 7157        PROC : db2sysc
    16
    INSTANCE: db2p002              NODE : 016         DB   :
    xxxxxxxx
    APPHDL  : 0-2269               APPID: GA204468.N006.036242163744
    AUTHID  : DBAUTH
    EDUID   : 7157                 EDUNAME: db2agntp (DBNAME) 16
    FUNCTION: DB2 UDB, base sys utilities,
    sqeLocalDatabase::FirstConnect,
    probe:1516
    MESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG
              "No Storage Available for allocation"
              DIA8305C Memory allocation failure occurred.
    DATA #1 : String, 286 bytes
    Failed to allocate the desired database shared memory set.
    Check to make sure the configured DATABASE_MEMORY + overflow
    does not exceed the maximum shared memory on the system.
    Attempting to start up with only the system buffer pools.
    Desired database shared memory set size is (bytes):
    DATA #2 : unsigned integer, 8 bytes
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The current design of deactivation/activation of a database  *
    *                                                              *
    * partition allows there to be a slight overlap where, at the  *
    *                                                              *
    * point where shared memory is allocated for the "new"         *
    * activation,                                                  *
    * shared memory from the previous activation has not yet been  *
    *                                                              *
    * freed.  Note that all activity is completed for the old      *
    *                                                              *
    * activation, it is just the shared memory itself that may not *
    * yet                                                          *
    * be freed.                                                    *
    *                                                              *
    *                                                              *
    *                                                              *
    * This may lead to diag.log messages such as the following     *
    * which                                                        *
    * indicate that we are exhausing shared memory resources:      *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2009-05-22-12.38.15.369802-240 I6841457A939      LEVEL:      *
    * Warning                                                      *
    *                                                              *
    *                                                              *
    * PID    : 106946              TID  : 7157        PROC :       *
    * db2sysc                                                      *
    * 16                                                           *
    *                                                              *
    * INSTANCE: db2p002              NODE : 016        DB  :       *
    *                                                              *
    * xxxxxxxx                                                     *
    *                                                              *
    * APPHDL  : 0-2269              APPID:                         *
    * GA204468.N006.036242163744                                   *
    *                                                              *
    *                                                              *
    * AUTHID  : DBAUTH                                             *
    *                                                              *
    *                                                              *
    *                                                              *
    * EDUID  : 7157                EDUNAME: db2agntp (DBNAME) 16   *
    *                                                              *
    *                                                              *
    *                                                              *
    * FUNCTION: DB2 UDB, base sys utilities,                       *
    *                                                              *
    * sqeLocalDatabase::FirstConnect,                              *
    *                                                              *
    * probe:1516                                                   *
    *                                                              *
    *                                                              *
    *                                                              *
    * MESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG              *
    *                                                              *
    *                                                              *
    *                                                              *
    *           "No Storage Available for allocation"              *
    *                                                              *
    *                                                              *
    *                                                              *
    *           DIA8305C Memory allocation failure occurred.       *
    *                                                              *
    *                                                              *
    *                                                              *
    * DATA #1 : String, 286 bytes                                  *
    *                                                              *
    *                                                              *
    *                                                              *
    * Failed to allocate the desired database shared memory set.   *
    *                                                              *
    *                                                              *
    *                                                              *
    * Check to make sure the configured DATABASE_MEMORY + overflow *
    *                                                              *
    *                                                              *
    *                                                              *
    * does not exceed the maximum shared memory on the system.     *
    *                                                              *
    *                                                              *
    *                                                              *
    * Attempting to start up with only the system buffer pools.    *
    *                                                              *
    *                                                              *
    *                                                              *
    * Desired database shared memory set size is (bytes):          *
    *                                                              *
    *                                                              *
    *                                                              *
    * DATA #2 : unsigned integer, 8 bytes                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 9.7 fp4                                       *
    ****************************************************************
    

Problem conclusion

  • With the fix in v9.7 fp4, the memory issue associated with
    deactivation/activation
    of a database should no longer occur.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC73419

  • 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

    2010-12-21

  • Closed date

    2011-04-29

  • Last modified date

    2012-08-20

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

    IC70826

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC73419

Modified date: 20 August 2012