DB2 - Problem description
Problem IC87833 | Status: Closed |
IF THE TOTAL NUMBER OF STATISTIC EVENT LOG FILES IS 15, DB2DIAG AND PD_GET_DIAG_HIST FAIL TO RETRIEVE DATA. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description Above * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10 Fix Pack 2 * **************************************************************** | |
Local Fix: | |
Remove any older statistic event log files so the total number of logs is 15 or less. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2012 28.08.2013 28.08.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |