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

LINUX ONLY: DB2GCF MIGHT REPORT INCORRECT STATUS DUE TO ASLR.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The db2gcf command might report instance state as Operable even 
if the instance is up and running. 
For example: 
$ db2start 
SQL1063N  DB2START processing was successful. 
 
$ db2gcf -s -p 0 
DB2 State 
Member 0 :  Operable 
 
The db2gcf command should report 'Available' if the instance is 
up. 
 
Users can see the db2diag.log entries like as below, it 
indicates shmat() subroutine failed due to ASLR (Address space 
layout randomization) feature in Linux operating system. 
DB2 supports ASLR in V10.1 or later, so db2gcf should handle the 
error properly. 
 
2014-11-12-07.00.02.883719+540 I1809214E1556         LEVEL: 
Severe (OS) 
PID     : 52512                TID : 140265087063840 PROC : 
db2gcf 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: host1 
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:210 
MESSAGE : ZRC=0x850F00C4=-2062614332=SQLO_ADDR_CONFLICT 
          "An address space conflict was detected attaching to 
shared memory." 
CALLED  : OS, -, shmat                            OSERR: EINVAL 
(22) 
<snip> 
 
2014-11-12-07.00.03.023101+540 E1810771E673          LEVEL: 
Error 
PID     : 52512                TID : 140265087063840 PROC : 
db2gcf 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: host1 
FUNCTION: DB2 UDB, high avail services, sqlhaInternalDbmsAttach, 
probe:209 
RETCODE : ZRC=0x850F00C4=-2062614332=SQLO_ADDR_CONFLICT 
          "An address space conflict was detected attaching to 
shared memory." 
<snip>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5                              * 
****************************************************************
Local Fix:
Disable ASLR in the Linux system.
Solution
Fixed in DB2 version 10.1.0.5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.12.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)


Problem solved according to the fixlist(s) of the following version(s)


10.1.0.5

FixList