|
Problem IC96271
|
Status: Closed |
STMM ON 32-BIT INSTANCE PLATFORM MAY FAIL TO UPDATE PCKCACHESZ WHEN IT IS WORKING ON 64-BIT WINDOWS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When DB2 STMM is working for a database of db2 32-bit instance
on 64-bit Windows, DB2 STMM fails to update PCKCACHESZ db cfg
parameters with over limited value for 32-bit instance as below.
2013-02-13-13.27.12.006000+540 I1152713H977 LEVEL: Event
PID : 8052 TID : 7536 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : DB01
APPHDL : 0-20 APPID: *LOCAL.DB2.130213025200
AUTHID : DB2ADMIN
EDUID : 7536 EDUNAME: db2stmm (DB01)
FUNCTION: DB2 UDB, Self tuning memory manager,
stmmLogRecordBeforeResizes, probe:590
DATA #1 : String, 525 bytes
*** stmmCostBenefitRecord ***
Type: PCKCACHESZ
PageSize: 4096
Saved Misses: 11
Benefit:
-> Simulation size: 8913
-> Total seconds saved: 2 (+ 326322613 ns)
-> Normalized seconds/page: 1.32525E-006
Cost:
-> Simulation size: 8913
-> Total seconds saved: 2 (+ 326322613 ns)
-> Normalized seconds/page: 1.32525E-006
Current Size: 89122
Minimum Size: 2095
Potential Increase Amount: 44561
Potential Increase Amount From OS: 44561
Potential Decrease Amount: 17824
Pages Available For OS: 17824
Interval Time: 196.947
2013-02-13-13.27.12.022000+540 I1156264H635 LEVEL: Error
PID : 8052 TID : 7536 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : DB01
APPHDL : 0-20 APPID: *LOCAL.DB2.130213025200
AUTHID : DB2ADMIN
EDUID : 7536 EDUNAME: db2stmm (DB01)
FUNCTION: DB2 UDB, Self tuning memory manager,
stmmUpdateDBConfig, probe:275
MESSAGE : ZRC=0x82AE00A7=-2102525785=STMM_CONFIG_UPDATE_FAILED
"An attempted configuration update failed"
DATA #1 : String, 74 bytes
Error updating parameter Pckcachesz, updateValue = 133683,
sqlcode = -5131 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 32-bit instance user on 64-bit Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 Version 10.1 FixPack 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 |
Problem was first fixed in Version 10.1 FixPack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2013
03.10.2013
03.10.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
|
 |
| 10.1.0.3
|
|
