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

DB2GCF MAY ENCOUNTER MEMORY ISSUES WHEN USED WITH ASLR ON LINUX

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If the db2gcf process encounters this issue, a Severe error 
message similiar to the following will be seen in the 
db2diag.log: 
 
2012-02-12-05.06.30.931347+480 I18439037E1487      LEVEL: Severe 
(OS) 
PID     : 55238                TID  : 46982620153456PROC : 
db2gcf 
INSTANCE: db2inst4             NODE : 000 
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:210 
MESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG 
          "No Storage Available for allocation" 
          DIA8305C Memory allocation failure occurred. 
CALLED  : OS, -, shmat                            OSERR: EINVAL 
(22) 
DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes 
0x00007FFF588B27F0 : 0000 0000 0200 0000 0000 0000 0200 0000 
................ 
0x00007FFF588B2800 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007FFF588B2810 : 0000 2603 0000 0000 0880 0701 0000 0000 
..&............. 
DATA #2 : Memory set ID, PD_TYPE_OSS_MEM_SET_ID, 4 bytes 
0x0000000200001DC0 : 1300 4B20 
..K 
DATA #3 : Pointer, 8 bytes 
0x00002abaecd61000 
CALLSTCK: 
  [0] 0x00002ABAFB2B7A4D pdLogSysRC + 0x239 
  [1] 0x00002ABAFB37BF20 sqlocshr + 0x752 
  [2] 0x00002ABB00EF785C 
_Z21sqlhaMonitorPartitionP13sqlo_nodeline + 0x2CC 
  [3] 0x00002ABB00EF74B5 _Z22sqlhaMonitorNodeNumbers + 0x155 
  [4] 0x00002ABB00EF1CB1 gcf_getstate + 0x1FCD 
  [5] 0x00002ABAFABF93A1 
_ZN9GcfCaller8getStateEP12GCF_PartInfomP11GCF_RetInfo + 0x1B7 
  [6] 0x0000000000403A4E main + 0x1026 
  [7] 0x000000338761D994 __libc_start_main + 0xF4 
  [8] 0x0000000000402999 __gxx_personality_v0 + 0xD1 
  [9] 0x0000000000000000 ?unknown + 0x0 
 
This is due to db2gcf not properly handling the Linux Address 
Space Layout Randomization (ASLR) feature. 
 
This is the same issue as documented in the following link: 
http://www-01.ibm.com/support/docview.wss?uid=swg21365583
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 HA(TSA) users on Linux with ASLR enabled                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 FP3                              * 
****************************************************************
Local Fix:
Refer to the "Resolving the problem" section of the following 
link: 
http://www-01.ibm.com/support/docview.wss?uid=swg21365583
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
Fixed in DB2 version 10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.01.2013
01.10.2013
01.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 FixList
10.1.0.3 FixList