home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC70826 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF                                                          * 
**************************************************************** 
* 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.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.5.0.7 or higher                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed DB2 v9.5.0.7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73419 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2010
19.10.2010
19.10.2010
Problem solved at the following versions (IBM BugInfos)
9.5.0.7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList