DB2 - Problem description
Problem IT16904 | Status: Closed |
THE DB2EGCF PROCESS MAY FAIL TO ATTACH TO THE SHARED MEMORY SEGMENT IF THE OS ASLR FEATURE IS ENABLED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
If the OS address space layout randomization (ASLR) feature is enabled, then the db2egcf process may fail to attach to the shared memory segment leading to a db2egcf failure. If this issue is hit, then the following error will appear in the db2diag.log file: 2016-02-01-04.49.35.554345+000 I964152A1024 LEVEL: Error PID : 15204492 TID : 1 PROC : db2egcf INSTANCE: db2inst1 NODE : 000 EDUID : 1 FUNCTION: <0>, <0>, <0>, probe:100 MESSAGE : ZRC=0x850F009A=-2062614374=SQLO_ADDR_CONFLICT "An address space conflict was detected attaching to shared memory." DATA #1 : String, 22 bytes sqlocshr.-2062614374.. CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x09000000090DA1BC pdOSSeLoggingCallback + 0x34 [1] 0x0900000007F8B9C4 oss_log__FP9OSSLogFacUiN32UlN26iPPc + 0x1C4 [2] 0x0900000007F8B7B0 ossLog + 0xD0 [3] 0x0000000100001224 db2haAttachToDatabase__FPcP9SQLE_KRCBPP16sqeLocalDatabase + 0x324 [4] 0x00000001000015C0 db2haGetHADRState__FPcP9HDR_STATET1 + 0x60 [5] 0x000000010000263C main + 0x77C [6] 0x0000000100000320 __start + 0x98 [7] 0x0000000000000000 ?unknown + 0x0 [8] 0x0000000000000000 ?unknown + 0x0 [9] 0x0000000000000000 ?unknown + 0x0 If this issue occurs in an automated(TSA) DB2 environment, it may trigger an unexpected failover due to db2gcf being unable to determine the state of the DB2 instance. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 8 * **************************************************************** | |
Local Fix: | |
Disable the address space layout randomization (ASLR) feature. | |
Solution | |
First fixed in DB2 10.5 Fix Pack 8 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.09.2016 13.03.2017 13.03.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |