DB2 - Problem description
Problem IC87014 | Status: Closed |
DATABASE MEMORY SET ID DISPLAYED BY DB2PD -MEMSETS IS NOT CORRECT | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The database memory set id displayed by db2pd -memsets is not correct. Taking ipcs -ma output to match the memory set id for the database memory set is no longer possible. For example database SAMPLE memory set id '1159733248' displayed by db2pd will not show up in the ipcs output: Memory Sets: Name Address Id Size(Kb) Key DBMS 0x0780000000000000 551551095 316480 0xC3DC4961 SAMPLE 0x0000000000000000 1159733248 188992 0x0 FMP 0x0780000020000000 686817346 22592 0x0 AppCtl 0x0700000040000000 92274739 160064 0x0 Trace 0x0770000000000000 638582900 131586 0xC3DC4974 PRIVATE 0x0000000110056050 0 17920 0x0 $ ipcs -ma | grep -i db2v10 m 922746909 0xffffffff --rw------- db2v1010 db2grp1 db2v1010 db2grp1 m 92274739 0xffffffff --rw------- db2v1010 db2grp1 db2v1010 db2grp1 m 442499131 0xffffffff --rw------- db2v1010 db2grp1 db2v1010 db2grp1 m 686817346 0xffffffff --rw------- db2v1010 db2grp1 db2v1010 db2grp1 m 638582900 0xc3dc4974 --rw-rw-rw- db2v1010 db2grp1 db2v1010 db2grp1 m 551551095 0xc3dc4961 --rw------- db2v1010 db2grp1 db2v1010 db2grp1 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * 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 | |
Solution | |
First fixed in DB2 Version 10.1 FixPack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.10.2012 07.10.2013 07.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 |