DB2 FOR LUW / DB2FORLUW / 970 - DB2

Under rare circumstances, incorrect checking for a null pointer, 
in activity metrics termination can cause an instance crash. 
The trap file created will contain a stack similar to the 
following: 
 
0        sqlmTermActivityMetrics.fdpr.clone.18 
1        sqlrr_activity_exe_stop 
2        sqlrr_activity_exe_stop 
3        sqlrr_open (engn/sqr/sqlrr_req_sql.C) 
4        sqljs_ddm_opnqry 
5        sqljsParseRdbAccessed 
6        sqljsParse.fdpr.clone.287 
7        sqljsSqlam 
8        sqljsDriveRequests 
9        sqljsDrdaAsInnerDriver 
10       sqljsDrdaAsDriver 
11       sqeAgent::RunEDU 
12       sqzEDUObj::EDUDriver 
13       sqloEDUEntry 
 
The database configuration parameter MON_ACT_METRICS 
would have to be set to NONE for it to be possible to 
encounter this trap.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Under rare circumstances, incorrect checking for a null      * 
* pointer, in activity metrics termination can cause an        * 
* instance crash.                                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the current fixpack                               * 
****************************************************************

One possible work around to avoid hitting this trap is to set 
the database configuration parameter MON_ACT_METRICS to BASE. 
This is configurable online. There is a potential for you to 
notice a small performance degradation (< 3% worst case) when 
you enable activity metrics collection. 
 
MON_ACT_METRICS is documented here: 
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?t 
opic=/com.ibm.db2.luw.admin.config.doc/doc/r0054936.html

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
 

The database configuration parameter MON_ACT_METRICS would have 
to be set to NONE for it to be possible to encounter this trap.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC73203 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

01.10.2010
11.09.2011
11.09.2011