home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC81500 Status: Closed

ENGINE TRAP WITH ENTRYCALLBACK AND ATMGETHARDENINGLIST IN THE CALLSTACK

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Under rare conditions, you might experience a trap from 
automatic statistics collection processing.  Automatic 
statistics collection is enabled via the AUTO_RUNSTATS database 
configuration parameter.  This trap is rare because for it to 
occur, a memory allocation error must occur in a specific 
codepath.  When the trap occurs, it will have functions 
entryCallback and atmGetHardeningList in the call stack, for 
example: 
 
0        ossDumpStackTraceEx 
1        OSSTrapFile::dumpEx 
2        sqlo_trce 
3        sqloEDUCodeTrapHandler 
4        __pthread_mutex_cond_lock 
5        entryCallback 
6        sqlrlc_foreach 
7        atmGetHardeningList 
8        atmAPI 
9        sqlrr_atm 
10      atmAPIEntry 
11      sqlerKnownProcedure 
 
This problem was first introduced in DB2 Version 9.7 Fixpack 1.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Under rare conditions, you might experience a trap from      * 
* automatic statistics collection processing.  Automatic       * 
* statistics collection is enabled via the AUTO_RUNSTATS       * 
* database                                                     * 
* configuration parameter.  This trap is rare because for it   * 
* to                                                           * 
* occur, a memory allocation error must occur in a specific    * 
* codepath.  When the trap occurs, it will have functions      * 
* entryCallback and atmGetHardeningList in the call stack, for * 
* example:                                                     * 
*                                                              * 
* 0        ossDumpStackTraceEx                                 * 
* 1        OSSTrapFile::dumpEx                                 * 
* 2        sqlo_trce                                           * 
* 3        sqloEDUCodeTrapHandler                              * 
* 4        __pthread_mutex_cond_lock                           * 
* 5        entryCallback                                       * 
* 6        sqlrlc_foreach                                      * 
* 7        atmGetHardeningList                                 * 
* 8        atmAPI                                              * 
* 9        sqlrr_atm                                           * 
* 10      atmAPIEntry                                          * 
* 11      sqlerKnownProcedure                                  * 
*                                                              * 
* This problem was first introduced in DB2 Version 9.7 Fixpack * 
* 1.                                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fixpack 6.                        * 
****************************************************************
Local Fix:
Disable AUTO_RUNSTATS, which is an online configurable db cfg 
parameter.  When disabled, you need to consider performing 
statistics collection manually as needed, until automatic 
statistics collection can be re-enabled.
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in DB2 Version 9.7 Fixpack 6.
Workaround
See Local Fix.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84515 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.02.2012
11.06.2012
11.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList