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 IC74680 Status: Closed

STMM TUNING CHANGES FAIL FREQUENTLY IN DPF ENVIRONMENTS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Errors in STMM assumptions during the final validation stage 
cause tuning changes to fail unnecessarily in a DPF environment. 
This forces a rollback of successfully applied tuning changes 
across all partitions. 
These errors may be repetitive - they may occur every tuning 
cycle for long periods of time. 
Note that in cases of very disparate memory usage across 
partitions/nodes, these errors may be expected, as STMM does not 
tune non-homogenous partition groups effectively 
 
Example db2diag.log entries: 
 
2010-12-01-01.53.47.222586-300 E5004760A640       LEVEL: Warning 
PID     : 1929398              TID  : 47742       PROC : db2sysc 
7 
INSTANCE: db2inst1               NODE : 007         DB   : 
SAMPLE 
APPHDL  : 3-53                 APPID: *N3.DB2.101024132210 
AUTHID  : db2inst1 
EDUID   : 47742                EDUNAME: db2agntp (SAMPLE) 7 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmCheckIfFreeMemoryIsEnoughForSizeIncr, probe:663 
MESSAGE : ZRC=0xFFFFEC49=-5047 
DATA #1 : String, 147 bytes 
There is not enough free memory for size increase. Free memory 
in pages: Physical memory = 4838, Instance memory = 314147, 
Database memory = 265040 
 
2010-12-01-01.53.47.230116-300 I5005901A850       LEVEL: Error 
PID     : 1929398              TID  : 47742       PROC : db2sysc 
7 
INSTANCE: db2inst1               NODE : 007         DB   : 
SAMPLE 
APPHDL  : 3-53                 APPID: *N3.DB2.101024132210 
AUTHID  : db2inst1 
EDUID   : 47742                EDUNAME: db2agntp (SAMPLE) 7 
FUNCTION: DB2 UDB, config/install, sqlfPdbUpdResetDbCfg, 
probe:1571 
MESSAGE : ZRC=0xFFFFEC49=-5047 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -5047   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL09055 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000007 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2010-12-01-01.53.47.718020-300 I5031657A911       LEVEL: Error 
PID     : 1904822              TID  : 3600        PROC : db2sysc 
3 
INSTANCE: db2inst1               NODE : 003         DB   : 
SAMPLE 
APPHDL  : 3-53                 APPID: *N3.DB2.101024132210 
AUTHID  : db2inst1 
EDUID   : 3600                 EDUNAME: db2stmm (SAMPLE) 3 
FUNCTION: DB2 UDB, config/install, sqlfPdbUpdDbCfgReq, 
probe:1246 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid :           sqlcabc: 0   sqlcode: -5124   sqlerrml: 1 
 sqlerrmc: 1 
 sqlerrp : 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000007 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #2 : String, 74 bytes 
Number of failed nodes: 61 
Nodes that failed: 4, 5, 6, 9, 10, and others.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF systems with Self-tuning of Database Memory enabled to   * 
* adapt to system memory availability INSTANCE_MEMORY =        * 
* AUTOMATIC                                                    * 
* DATABASE_MEMORY = AUTOMATIC SELF_TUNING_MEM = ON             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5                        * 
****************************************************************
Local Fix:
available fix packs:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 9.7 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.02.2011
22.05.2012
22.05.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList