DB2 FOR LUW / DB2FORLUW / 970 - DB2

We can specify the max number of statistic event log is 15 (e.g. 
db2set DB2_OPTSTATS_LOG=ON,NUM=15 ) but when the total number of 
statistic event log files reached is 15 ( e.g.: 
db2optstats.0.log , ... , db2optstats.14.log ), db2diag command 
and PD_GET_DIAG_HIST against statistic event log will fail to 
retrieve any data. 
 
Example: 
 
>db2diag -fac optstats -c 
db2diag: No messages found for facility "optstats". 
 
>db2 "SELECT FACILITY, RECTYPE, TIMESTAMP, IMPACT, SUBSTR(MSG,1, 
50) AS MSG FROM TABLE (PD_GET_DIAG_HIST( 'OPTSTATS', 'E', '', 
NULL, NULL) )" 
SELECT FACILITY, RECTYPE, TIMESTAMP, IMPACT, SUBSTR(MSG,1, 50) 
AS MSG FROM TABLE (PD_GET_DIAG_HIST( 'OPTSTATS', 'E', '', NULL, 
NULL) ) 
 
FACILITY             RECTYPE TIMESTAMP                  IMPACT 
MSG 
-------------------- ------- -------------------------- 
------------------ 
-------------------------------------------------- 
 
  0 record(s) selected.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.7 FP7 or subsequent fix pack                    * 
****************************************************************

Remove any older statistic event log files so the total number 
of logs is 15 or less.

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
 

First Fixed In DB2 Version 9.7 Fix Pack 7

keiner bekannt / siehe Local-Fix

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

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

02.04.2012
17.01.2013
17.01.2013

9.7.FP7