|
Problem IC95300
|
Status: Geschlossen |
PREVENT MESSAGE FROM FUNCTION STMMSIMULATEHJPACKPARTITIONS, PROBE:3555, FROM BEING DUMPED INTO DB2DIAG.LOG |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
With the self-tuning memory manager (STMM) enabled, the
following message might be logged to the db2diag.log:
2013-04-01-09.15.02.883018+120 I943465A599 LEVEL:
Warning
PID : 16842778 TID : 168779 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-19546 APPID:
*LOCAL.db2inst1.130401071506
AUTHID : DB2INST1 HOSTNAME: MYHOST
EDUID : 168779 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, Self tuning memory manager,
stmmSimulateHJPackPartitions, probe:3555
DATA #1 : String, 112 bytes
Cannot continue - Estimated build size is 0.
Estimated build size= 0.00
Estimated probe size= 152000.00
The cause of this message does not necessarily mean that there
is an underlying DB2 problem, and should therefore not be logged
to the db2diag.log.
The fix for this APAR will move this message exclusively to the
STMM logs, where the message is already logged. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
Problem Fixed In 10.5.0.3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.08.2013
28.02.2014
28.02.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
