|
Problem IC68242
|
Status: Closed |
MESSAGE : UNABLE TO FIND DONOR TO SATISFY MINSIZE CONSTRAINT SHOULD BE INFO ONLY AND/OR MOVED TO STMM LOG |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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. |
| Problem Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
Problem first fixed in DB2 9.7 Fix Pack 3. The message will no
longer appear in db2diag.log. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.04.2010
20.09.2010
20.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
