home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC81500 Status: Geschlossen

ENGINE TRAP WITH ENTRYCALLBACK AND ATMGETHARDENINGLIST IN THE CALLSTACK

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
This problem was first fixed in DB2 Version 9.7 Fixpack 6.
Workaround
See Local Fix.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84515 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.02.2012
11.06.2012
11.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList