Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT11292 Status: Closed

FODC CRASH DIAGNOSTICS IMPROVEMENTS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Two improvements are delivered with this APAR : 
 
1. When DB2 crashes due to a problem not in instance scope (the 
db2agent encountering the problem is not associated with a 
database), the underlying FODC callout script does not execute 
properly, and expected diagnostics from the script are not 
generated.  This includes the shared memory dump if DUMPSHM=YES 
is configured. 
 
2. It is not intended to dump the "dirty page" details when 
db2pd -db <database> is executed.  On larger systems this can be 
verbose and use up the entire 5 minute time limit for executing 
the db2pd command during crash diagnostics.  This will be fixed 
(only summary information will be provided for dirty pages)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems are impacted                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* This APAR affects serviceability only.  Upgrade to DB2       * 
* Version 10.5 Fix Pack 7                                      * 
****************************************************************
Local Fix:
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       :
17.09.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 FixList