DB2 - Problem description
Problem IC75140 | 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 / 970 - 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: * * DB2 on Solaris * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See Local Fix * **************************************************************** | |
Local Fix: | |
Set project.max-shm-memory to at least 2 X RAM, set shmmax to at least 1 X RAM | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 9.7 Fix Pack 5 | |
Workaround | |
See Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.03.2011 23.05.2012 23.05.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |