|
Problem IC61732
|
Status: Closed |
ADDING SUPPORT FOR AIX WPAR ENVIRONMENTS |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
This APAR is to add WPAR support for DB2 v9.1 and DB2 v9.5.
Without this change, memory management functions that query the
Operating System for memory information return information for
the machine without regard for the memory limitations of the
WPAR. This can cause DB2 to overallocate memory leading to out
of memory errors and/or excessive paging. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 on WPAR systems *
****************************************************************
* PROBLEM DESCRIPTION: *
* This APAR is to add WPAR support for DB2 v9.1 and DB2 v9.5. *
* Without this change, memory management functions that query *
* the Operating System for memory information return *
* information for the machine without regard for the memory *
* limitations of the WPAR. This can cause DB2 to overallocate *
* memory leading to out of memory errors and/or excessive *
* paging. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.5 FP6 or newer. *
**************************************************************** |
| Local Fix: |
The workaround for this issue is the following:
1) Set INSTANCE_MEMORY to a set value
2) Create the databases without resizable bufferpools
(AUTOCONFIGURE USING BP_RESIZEABLE NO APPLY NONE) |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
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 |
Upgrade to DB2 v9.5 FP6 or newer. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.06.2009
19.07.2010
19.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
