|
Problem IC73419
|
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 / 970 - 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 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 |
| 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 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
|
| Solution |
With the fix in v9.7 fp4, the memory issue associated with
deactivation/activation
of a database should no longer occur. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.12.2010
29.04.2011
20.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4,
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
