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

GLOBAL BENEFIT IS INVALID

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Customer running STMM on linux390 see GLOBAL BENEFIT IS INVALID 
errors every three minutes in the diaglog: 
 
2017-02-15-15.59.38.875734-120 I146807476A697       LEVEL: Error 
PID     : 8695                 TID : 4396003879184  PROC : 
db2sysc 0 
INSTANCE: db2i66p              NODE : 000           DB   : 
D1CGN01 
APPHDL  : 0-10                 APPID: *LOCAL.DB2.161123103626 
AUTHID  : DB2CGN11             HOSTNAME: pzl1db200124 
EDUID   : 51                   EDUNAME: db2stmm (D1CGN01) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmGetGlobalBenefit, probe:2363 
MESSAGE : 
ZRC=0x82AE0093=-2102525805=STMM_DBMEM_INVALID_GLOBAL_BENEFIT 
          "Global benefit is invalid" 
DATA #1 : String, 102 bytes 
STMM global benefit structure size mismatch.  Structure ends at 
0x3ff863fb3a0, expected 0x3ff863fb390. 
 
2017-02-15-15.59.38.875873-120 I146808174A646       LEVEL: 
Warning 
PID     : 8695                 TID : 4396003879184  PROC : 
db2sysc 0 
INSTANCE: db2i66p              NODE : 000           DB   : 
D1CGN01 
APPHDL  : 0-10                 APPID: *LOCAL.DB2.161123103626 
AUTHID  : DB2CGN11             HOSTNAME: pzl1db200124 
EDUID   : 51                   EDUNAME: db2stmm (D1CGN01) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmUpdateGlobalBenefit, probe:3289 
MESSAGE : 
ZRC=0x82AE0093=-2102525805=STMM_DBMEM_INVALID_GLOBAL_BENEFIT 
          "Global benefit is invalid" 
DATA #1 : String, 47 bytes 
STMM global benefit is corrupt, reinitializing.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in DB2 11.1 Mod 2 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.04.2017
23.06.2017
23.06.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)