home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC91913 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95300 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.04.2013
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList