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 IC72970 Status: Closed

ON SOLARIS, DB2OSCONF SHOULD REPORT 2 X RAM FOR
PROJECT.MAX-SHM-MEMORY.SHMMAX RECOMMENDATION SHOULD BE IN BYTES, NOT 4K
UNITS.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Two problems will be fixed in the db2osconf tool for Solaris. 
 
1. Since version 9.5, shared memory virtual limits need to be 
higher than the existing recommendation of 90% * RAM for many 
standard configurations.  This is due to additional virtual 
shared memory preallocation per instance and database, and 
volatility in STMM environments with many multiple databases. 
 
2. A separate problem is that  the shmmax recommendation (size 
of a single segment) is reported in 4K units, not bytes.  The 
setting should be reported in bytes.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems running DB2 on Solaris                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Configure Solaris kernel settings as per APAR Error          * 
* Description.                                                 * 
****************************************************************
Local Fix:
available fix packs:
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 in DB2 Version 9.5 Fix Pack 8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC75140 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.12.2010
11.08.2011
11.08.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList