|
Problem IC95290
|
Status: Closed |
DB2VEND PROCESS CAN FAIL TO ATTACH SERVER (DATABASE MEMORY SET) SHARED MEMORY SEGMENT (SQLO_ADDR_CONFLICT IN DB2DIAG.LOG) |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In some cases the db2vend process might fail to attach server
shared memory segments that belong
to the database memory set. Messages like the following will
appear in the db2diag.log file:
2013-03-11-11.31.34.862818-240 I89558391A1173 LEVEL:
Warning (OS)
PID : 2622752 TID : 1 PROC :
db2vend
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) "Invalid argument"
DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes
This will happen only in a few cases where the db2vend stays
alive long enough for
the database server to grow the database memory set with a few
additional shared memory
segments. The problem here is that the db2vend will somehow try
to attach again a segment
it already attached at that given address. Note that to
differentiate this from a genuine error
a truss/trace/strace... would show that the db2vend is trying to
shmat() a segment with segid ID
at address ADDR but a pmap would already show that same segment
with segid ID attached
at address ADDR.
When that problem occurs, if the db2vend stays alive long enough
multiple occurrences of
this message will appear in the db2diag.log. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL DB2 VERSION 10.5 USERS *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.5 FIXPACK 3 *
**************************************************************** |
| Local Fix: |
Deactivate/Activate database. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In DB2 10.5 FIXPACK 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
28.04.2014
28.04.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
