|
Problem IT10019
|
Status: Closed |
DUMPSHM OPTION FOR DB2FODC MAY MISS MUCH OF SHARED MEMORY FOR CONFIGURATIONS LARGER THAN 4GB |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When the new compact shared memory dump option is set
(DB2FODC="DUMPSHM=ON") and DB2 abends, DB2 dumps significant
areas of shared memory to a a binary dump file in the FODC
folder. When the configuration of a memory set is larger than
4GB (the most common case being database memory), important
portions of shared memory may be missed. This may result in
support being unable to determine the root cause for the abend. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All UNIX systems are vulnerable *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* This issue affects a serviceability feature only. Upgrade *
* to DB2 Version 10.5 Fix Pack 7 *
**************************************************************** |
| Local Fix: |
avoid using the DUMPSHM option - used in conjunction with
CORESHM=NO. Rely on the default full coredump behaviour (do not
set CORESHM=NO). |
| Solution |
Problem first fixed in DB2 Version 10.5 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.07.2015
16.02.2016
16.02.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
