DB2 - Problembeschreibung
Problem IC75140 | Status: Geschlossen |
ON SOLARIS, DB2OSCONF SHOULD REPORT 2 X RAM FOR PROJECT.MAX-SHM-MEMORY.SHMMAX RECOMMENDATION SHOULD BE IN BYTES, NOT 4K UNITS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 Version 9.7 Fix Pack 5 | |
Workaround | |
See Local Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.03.2011 23.05.2012 23.05.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |