DB2 FOR LUW / DB2FORLUW / A50 - DB2

DB2 AUTO REORG may fail to evaluate ITC (Insert Time Clustering) 
tables and cause SQLCODE -960 (SQL0960N) errors in db2diag.log: 
 
2016-09-12-01.36.10.332692+120 I846576A571          LEVEL: Error 
PID     : 40960108             TID : 1239           PROC : 
db2acd 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPID   : *LOCAL.db2inst1.160910162203 
HOSTNAME: localhost 
EDUID   : 1239                 EDUNAME: db2acd 0 
FUNCTION: DB2 UDB, Health Monitor, db2HmonEvalReorg, probe:997 
MESSAGE : Failed to evaluate table "SSSSS"."ITCTAB". Probe 805 . 
SQLCODE = -960 
DATA #1 : Hexdump, 4 bytes 
0x00000001120DEE34 : FFFF FC40 
.. 
 
AND sometimes this as well: 
 
2016-08-30-09.44.08.243692+120 I1578561A573 LEVEL: Error 
PID : 40960108 TID : 2554 PROC : db2acd 0 
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE 
APPID : *LOCAL.db2inst1.160830042201 
HOSTNAME: localhost 
EDUID : 2554 EDUNAME: db2acd 0 
FUNCTION: DB2 UDB, Health Monitor, db2HmonEvalReorg, probe:997 
MESSAGE : Failed to evaluate table "SSSSS "."TTTTTT". Probe 535 
. 
SQLCODE = -960 
DATA #1 : Hexdump, 4 bytes 
0x0000000113935E34 : FFFF FC40 ...@ 
 
The SQL0960N error is caused by a endless loop that creates temp 
tables in SYSTOOLSTMPSPACE till it's limit of objects is 
reached. 
 
Note: The message in 'Probe 535' is a subsequent error caused by 
the original problem in 'Probe 805' and may not necessarily show 
an ITC table (it could be any table).

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************

First fixed in Db2 10.5 Fix Pack 9

not known / see Local fix

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

28.10.2016
29.09.2017
29.09.2017

9.0.