home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC68242 Status: Geschlossen

MESSAGE : UNABLE TO FIND DONOR TO SATISFY MINSIZE CONSTRAINT SHOULD BE
INFO ONLY AND/OR MOVED TO STMM LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Warning messages similar to the following can occur regularly in 
the db2diag.log on databases when database_memory is not 
automatic and small in size : 
 
2010-03-09-15.07.04.957252+060 I2581005A477       LEVEL: Warning 
PID     : 2076718              TID  : 4113        PROC : db2sysc 
1 
INSTANCE: db2inst1             NODE : 000         DB   : sample 
APPHDL  : 1-51                 APPID: *A1.DB2.123456789 
AUTHID  : DB2INST1 
EDUID   : 4113                 EDUNAME: db2stmm (SAMPLE) 1 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmEnforceMinSizeConstraints, probe:2358 
MESSAGE : Unable to find donor to satisfy minSize constraint 
 
The message can be ignored as it is intended to be information 
only.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using STMM                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Warning messages similar to the following can occur          * 
* regularly in                                                 * 
* the db2diag.log on databases when database_memory is not     * 
* automatic and small in size :                                * 
*                                                              * 
* 2010-03-09-15.07.04.957252+060 I2581005A477      LEVEL:      * 
* Warning                                                      * 
* PID    : 2076718              TID  : 4113        PROC :      * 
* db2sysc 1                                                    * 
* INSTANCE: db2inst1            NODE : 000        DB  : sample * 
* APPHDL  : 1-51                APPID: *A1.DB2.123456789       * 
* AUTHID  : DB2INST1                                           * 
* EDUID  : 4113                EDUNAME: db2stmm (SAMPLE) 1     * 
* FUNCTION: DB2 UDB, Self tuning memory manager,               * 
* stmmEnforceMinSizeConstraints, probe:2358                    * 
* MESSAGE : Unable to find donor to satisfy minSize constraint * 
*                                                              * 
* The message can be ignored as it is intended to be           * 
* information                                                  * 
* only.                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fix Pack 3 to resolve this problem.       * 
****************************************************************
Local-Fix:
This message can be ignored.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 9.7 Fix Pack 3.  The message will no 
longer appear in db2diag.log.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.04.2010
20.09.2010
20.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList