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

DB2PD -DB <DBNAME> -MEMSET SHOWS INCORRECT ADDRESS FOR APPLICATION
MEMORY

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Database Partition 0 -- Database SUZHOU -- Active -- Up 0 days 
00:00:01 
 
Memory Sets: 
Name         Address    Id          Size(Kb)   Key         DBP 
Type   Unrsv(Kb)  Used(Kb)   HWM(Kb)    Cmt(Kb)    Uncmt(Kb) 
SUZHOU       0x40D1E000 1501003783  1740864    0x0         0 
1      555200     829760     829760     829760     911104 
AppCtl       0xAB12E000 1500971014  40064      0x0         0 
12     0          192        192        192        39872 
App26922     0x59768005 1500938245  128        0x0         0 
4      0          128        0          128        0 
 
The address for application memory is incorrect. It seems 
uses ID (0x59768005=1500938245) instead of the address of shared 
memory segment: 
4053d000    7172       -       -       - rwx--    [ anon ] 
40cd6000       4       -       -       - rwx--    [ anon ] 
40ce5000     128       -       -       - rwxs-    [ 
shmid=0x59780008 ] 
40d05000       4       -       -       - rwx--    [ anon ] 
40d1e000 1740864       -       -       - rwxs-    [ 
shmid=0x59778007 ] 
ab12e000   40064       -       -       - rwxs-    [ 
shmid=0x59770006 ] 
ad84e000     128       -       -       - rwxs-    [ 
shmid=0x59768005 ] 
ad86e000    1024       -       -       - rwx--    [ anon ] 
ad96e000      40       -       -       - r-x-- 
IBMOSauthserver.so 
ad978000       8       -       -       - rwx-- 
IBMOSauthserver.so 
ad97a000     788       -       -       - r-x-- 
libcrypto.so.0.9.7 
ada3f000      64       -       -       - rwx-- 
libcrypto.so.0.9.7 
 
They are raw and don't have any MemSet structure, so we don't 
really have a specific address they must be attached at. 
In this case, we need to assign "N/A" instead of a miss-leading 
memory address.
Problem Summary:
Problem Description: 
DB2PD -DB <DBNAME> -MEMSET SHOWS INCORRECT ADDRESS FOR 
APPLICATION MEMORY 
 
Problem Summary: 
Database Partition 0 -- Database SUZHOU -- Active -- Up 0 days 
 
00:00:01 
 
Memory Sets: 
Name         Address    Id          Size(Kb)   Key         DBP 
Type   Unrsv(Kb)  Used(Kb)   HWM(Kb)    Cmt(Kb)    Uncmt(Kb) 
SUZHOU       0x40D1E000 1501003783  1740864    0x0         0 
1      555200     829760     829760     829760     911104 
AppCtl       0xAB12E000 1500971014  40064      0x0         0 
12     0          192        192        192        39872 
App26922     0x59768005 1500938245  128        0x0         0 
4      0          128        0          128        0 
 
The address for application memory is incorrect. It seems 
uses ID (0x59768005=1500938245) instead of the address of shared 
memory segment: 
4053d000    7172       -       -       - rwx--    [ anon ] 
40cd6000       4       -       -       - rwx--    [ anon ] 
40ce5000     128       -       -       - rwxs-    [ 
shmid=0x59780008 ] 
40d05000       4       -       -       - rwx--    [ anon ] 
40d1e000 1740864       -       -       - rwxs-    [ 
shmid=0x59778007 ] 
ab12e000   40064       -       -       - rwxs-    [ 
shmid=0x59770006 ] 
ad84e000     128       -       -       - rwxs-    [ 
shmid=0x59768005 ] 
ad86e000    1024       -       -       - rwx--    [ anon ] 
ad96e000      40       -       -       - r-x-- 
IBMOSauthserver.so 
ad978000       8       -       -       - rwx-- 
IBMOSauthserver.so 
ad97a000     788       -       -       - r-x-- 
libcrypto.so.0.9.7 
ada3f000      64       -       -       - rwx-- 
libcrypto.so.0.9.7 
 
They are raw and don't have any MemSet structure, so we don't 
really have a specific address they must be attached at. 
In this case, we need to assign "N/A" instead of a miss-leading 
memory address.
Local Fix:
n/a
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 is first fixed in Version 9.7 Fixpack 4
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.11.2010
29.04.2011
29.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.