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

DPF: DB2PD -MEMSETS SHOWS INCORRECT KEY INFORMATION (DOES NOT MATCH WITH
IPCS -M OUTPUT) FOR PARTITIONS THAT ARE NOT 0.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
On a multi partition system, db2pd -memset -alldbp shows the 
key information for Partition 0 in all partitions: 
 
$ db2pd -alldbp -memsets -alldbp 
 
Database Partition 0 -- Active -- Up 119 days 00:10:51 -- Date 
06/20/2012 17:19:30 
 
Memory Sets: 
Name         Address            Id          Size(Kb)   Key 
DBP    Type   Unrsv(Kb)  Used(Kb)   HWM(Kb)    Cmt(Kb) 
Uncmt(Kb) 
DBMS         0x0000000200000000 201326592   35328 
0x9EE31D61  0      0      1600       9344       9536       35328 
0 
FMP          0x0000000210000000 83886201    22592      0x0 
0      0      2          0          960        22592      0 
 
Trace        0xFFFFFFEF00000000 1795162230  39257 
0x9EE31D74  0      -1     0          39257      0          39257 
0 
FCM          0x0000000220000000 1526726679  326848 
0x9EE31D62  0      11     268480     58368      74496 
326848     0 
 
Database Partition 1 -- Active -- Up 119 days 00:10:53 -- Date 
06/20/2012 17:19:30 
 
Memory Sets: 
Name         Address            Id          Size(Kb)   Key 
DBP    Type   Unrsv(Kb)  Used(Kb)   HWM(Kb)    Cmt(Kb) 
Uncmt(Kb) 
DBMS         0x0000000200000000 100663299   35328 
0x9EE31D61  1      0      1600       6464       6528       35328 
0 
FMP          0x0000000210000000 33554548    22592      0x0 
0      0      2          0          448        22592      0 
 
Trace        0xFFFFFFEF00000000 1795162230  39257 
0x9EE31D74  1      -1     0          39257      0          39257 
0 
FCM          0x0000000220000000 1526726679  326848 
0x9EE31D62  0      11     268480     58368      74496 
326848     0 
 
 
In the example above in Partition 1 we have for DBMS set a key 
of 0x9EE31D61 for ID 100663299. This is the same key for DBMS 
set in Partition 0. 
 
 
Ipcs shows for ID 100663299 : 
 
$ ipcs -m | grep 100663299 
m  100663299   0x9ee31f61 --rw------- db2inst4 db2iadm4 
 
The correct key is 0x9ee31f61 not 0x9EE31D61  for Partition 1. 
Partition 0 information is correct.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 and Fix Pack 7                    * 
****************************************************************
Local Fix:
available fix packs:
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 was first fixed in DB2 Version 9.7 and Fix Pack 7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC88311 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.06.2012
20.10.2012
20.10.2012
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList