|
Problem IT36748
|
Status: Closed |
DB2EGCF CAUSES TRACE FLOODING DUE TO MEMORY SEG FAULT
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
In a Db2 HA environment, when db2egcf with option "-h" is
called, a segmentation fault may be induced in the memory
causing trace flooding. The following message will be observed
in db2diag.log on the node.
2020-06-13-01.41.31.336279-240 I23415402E954 LEVEL:Error
PID : 19228 TID : 47838778077568 PROC
:db2egcf
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2hostname1
FUNCTION: , , , probe:100
MESSAGE : ZRC=0x850F00C4=-2062614332=SQLO_ADDR_CONFLICT
"An address space conflict was detected attaching to
shared memory."
DATA #1 : String, 22 bytes
sqlocshr.-2062614332..
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00002B82644CF84B
/opt/ibm/db2/V10.5/V11.1/lib64/libdb2osse.so.1 + 0x23F84B
[1] 0x00002B82644CF681 ossLog + 0xA1
[2] 0x0000000000403779
_Z21db2haAttachToDatabasePcP9SQLE_KRCBPP16sqeLocalDatabase +
0x249
[3] 0x0000000000403401 _Z17db2haGetHADRStatePcS_ + 0x1D1
[4] 0x0000000000402EE9 main + 0x8E9
[5] 0x00002B826529C495 __libc_start_main + 0xF5
[6] 0x0000000000402539 /usr/local/db2inst1/sqllib/bin/db2egcf
+ 0x2539 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.6.0 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.6.0 *
**************************************************************** |
| Comment |
First fixed in 11.5.6.0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.04.2021
08.12.2021
08.12.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
