DB2 FOR LUW / DB2FORLUW / 970 - DB2

If RUNSTATS is executed immediately after connecting to a 
database, subsequent operations may trap with a segmentation 
fault.  The subsequent operation can be any operation, including 
another RUNSTATS.  For the problem to occur, the RUNSTATS 
operation must be on a table without any indexes.  It does not 
matter if the runstats command specified an INDEX clause or not. 
 
Sample callstacks that can experience the problem: 
 
sqlr_audit 
sqlr_audit_context 
sqlrrcom_dps 
sqlrrcom 
sqlrr_commit 
 
and 
 
sqlr_audit 
sqlr_audit_checking 
sqlrr_check_auth 
sqlrrsta 
sqlrr_runstats_DA

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW on all supported platforms.                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* WITH ACTIVE DATABASE LEVEL AUDIT, PERFORMING RUNSTATS        * 
* RIGHTAFTER DATABASE BECOMES ACTIVE MAY TRAP.                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fix Pack 3                    * 
****************************************************************

Execute any SQL statement (e.g. "values 1") before running 
RUNSTATS.

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 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
 

Problem was first fixed in Version 9.7 Fix Pack 3

The problem will not occur if: 
(1) the table has at least one index, 
 
 
or 
(2) after CONNECT to database, if any SQL statement (e.g. 
 
VALUES(1)) 
has been executed before the RUNSTATS command.

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

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

27.05.2010
12.10.2010
16.11.2010

9.7.FP3