DB2 FOR LUW / DB2FORLUW / A10 - DB2

If a runstats is invoked against a user temporary table and the 
index clause explicitly specifies index names but omits the 
index schema name, i.e. index name is not fully-qualified, the 
instance crashes with a signal 11. 
 
db2diag.log entry indicates that a db2sysc process is brought 
down with a signal 11 (0x0B) 
 
e.g. 
 
2014-06-27-03.24.55.682213-240 E492764A469          LEVEL: Error 
PID     : 7930224              TID : 258            PROC : 
db2wdog 3 [db2inst1] 
INSTANCE: db2inst1               NODE : 003 
HOSTNAME: hostname 
EDUID   : 258                  EDUNAME: db2wdog 3 [db2inst1] 
FUNCTION: DB2 UDB, base sys utilities, sqleWatchDog, probe:8117 
DATA #1 : Process ID, 4 bytes 
9437226 
DATA #2 : Hexdump, 8 bytes 
0x0A000000003FDD80 : 0000 0101 0000 000B 
........ 
 
 
The stack becomes corrupted, and no FODC_Trap is generated. A 
core dump is generated, and db2sysc trapped in function strncpy 
(called by sqlrLocalRunstats). 
 
This problem exists only in v10.1; v9.7 and previous releases 
require fully-qualified index names in the index clause of the 
runstats command.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to v10.1 Fix Pack 5.                                  * 
****************************************************************

Modify the runstats command to use fully-qualified index names.

Fixed in v10.1 Fix Pack 5.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.07.2014
15.07.2015
15.07.2015