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 IC67203 Status: Geschlossen

PREVENT MESSAGE FROM FUNCTION STMMSIMULATEHJPACKPARTITIONS, PROBE:3505,
FROM BEING DUMPED INTO DB2DIAG.LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
With the self-tuning memory manager (STMM) enabled, the 
following message might be logged to the db2diag.log: 
 
2010-02-14-19.48.43.232491+060 I2760549A561 LEVEL: Warning 
PID : 25783 TID : 4399099212320PROC : db2sysc 
INSTANCE: db2inst NODE : 000 DB : MYDB 
APPHDL : 0-10095 APPID: 10.16.6.32.35445.100214175520 
AUTHID : DB2INST 
EDUID : 2049 EDUNAME: db2agent (MYDB) 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmSimulateHJPackPartitions, probe:3505 
DATA #1 : String, 107 bytes 
Cannot continue - Estimated build size is 0. 
Estimated build size= 0.00 
Estimated probe size= 0.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:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 2 in order to have       * 
* theSTMM-specific diagnostic message in question moved solely * 
* tothe STMM logs.                                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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 was first fixed in Version 9.7 Fix Pack 2. 
 
The diagnostic message, stmmSimulateHJPackPartitions 
 
 
probe:3505, will now only be logged to the STMM logs. 
 
 
Moreover, the LEVEL of the message will now be "Event" 
 
 
instead of "Warning".
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC91913 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.03.2010
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList