IT21932: ADDRESS SPACE CONFLICT MAY OCCUR IN DB2GCF IF ASLR IS ENABLED

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• The following message may occur in the db2diag.log if ASLR is
  enabled in Linux:
  
  2017-03-22-14.56.51.192796+060 I145511452E1550       LEVEL:
  Severe (OS)
  PID     : 9005                 TID : 140334003136288 PROC :
  db2gcf
  INSTANCE: db2s03               NODE : 000
  HOSTNAME: MYHOST1
  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)
  DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes
  0x00007FFC118F6FB8 : 0000 0000 0200 0000 0000 0000 0200 0000
  ................
  0x00007FFC118F6FC8 : 0000 0000 0000 0000 0000 0000 0000 0000
  ................
  0x00007FFC118F6FD8 : 0000 9309 0000 0000 0900 8E4D 0000 0000
  ...........M....
  DATA #2 : Memory set ID, PD_TYPE_OSS_MEM_SET_ID, 4 bytes
  0x000000020003AFD0 : 7700 F765
  w..e
  DATA #3 : Pointer, 8 bytes
  0x00007fa208bec000
  CALLSTCK: (Static functions may not be resolved correctly, as
  they are resolved to the nearest symbol)
    [0] 0x00007FA20B365E2E sqlocshr + 0x5BE
    [1] 0x00007FA20418B359
  _Z23sqlhaInternalDbmsAttachPA1_13__jmp_buf_tagP18SQLHA_SHMEM_HAN
  DLE + 0xE9
    [2] 0x00007FA20418DCEE
  _Z21sqlhaMonitorPartitionsmP23SQLO_PGRP_FILE_CONTENTS + 0xE8E
    [3] 0x00007FA204171123 gcf_getstate + 0x2463
    [4] 0x00007FA20DB1A4D9
  _ZN9GcfCaller8getStateEP12GCF_PartInfomP11GCF_RetInfo + 0x189
    [5] 0x0000000000403348 main + 0x1158
    [6] 0x00007FA209807C36 __libc_start_main + 0xE6
    [7] 0x0000000000402159 __gxx_personality_v0 + 0xC1
  
  2017-03-22-14.56.51.193542+060 E145513003E670        LEVEL:
  Error
  PID     : 9005                 TID : 140334003136288 PROC :
  db2gcf
  INSTANCE: db2s03               NODE : 000
  HOSTNAME: MYHOST1
  FUNCTION: DB2 UDB, high avail services, sqlhaInternalDbmsAttach,
  probe:226
  RETCODE : ZRC=0x850F00C4=-2062614332=SQLO_ADDR_CONFLICT
            "An address space conflict was detected attaching to
  shared memory."
  DATA #1 : unsigned integer, 2 bytes
  0
  DATA #2 : Database Partition Number, PD_TYPE_NODE, 2 bytes
  0
  DATA #3 : Database Partition Number, PD_TYPE_NODE, 2 bytes
  0
  DATA #4 : unsigned integer, 2 bytes
  0
  DATA #5 : unsigned integer, 2 bytes
  0
  DATA #6 : Boolean, 1 bytes
  true
  
  This APAR should relax this message.
  

Local fix

• The message can be ignored.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users.                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update to Db2 11.1 Mod 3 Fixpack 3.                          *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1 Mod 3 Fixpack 3.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IT20192

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP