|
Problem IC84515
|
Status: Closed |
ENGINE TRAP WITH ENTRYCALLBACK AND ATMGETHARDENINGLIST IN THE CALLSTACK |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 1. *
**************************************************************** |
| 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 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 10.1 Fix Pack 1. |
| Workaround |
See Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
01.11.2012
01.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
