Troubleshooting empty reports
This topic lists and explains several reasons why your report might not contain any report data. Use this information as a guide to identify possible reasons, including inappropriate command parameters.
At its core, OMEGAMON for Db2
Performance Expert identifies data to be collected and reported by IFCIDs. The
basic rule is that data to be reported needs to be collected and made available as input data to the
report generation process. If required IFCIDs are missing, the generated report ends with
DATA TO REPORT.
The problem of missing IFCIDs might also be caused by different versions of DB2 or OMEGAMON for Db2 Performance Expert. Both products might support different sets of IFCIDs, which can lead to situations where an IFCID is either not provided by a DB2 version or cannot be processed by an OMEGAMON for Db2 Performance Expert version. The same problem might arise if data from other sources, like SMF or GTF, is used for reports.
OMEGAMON for Db2 Performance Expert provides flexible means to specify which data to collect and which data to report. However, it provides no means to protect against inappropriate use of commands, subcommands and subcommand options, which also can result in empty reports.
The following sections list possible reasons why your report might end with a final message of
NO DATA TO REPORT.
Messages indicating unsupported IFCIDs or IFCID formats
If the job summary log shows message
FPEC4015I NUMBER OF RECORDS FROM UNSUPPORTED
RELEASES OF DB2 WAS ..., OMEGAMON for DB2 PE has detected IFCIDs in its
input data that it is not supposed to handle. Either the input data is from an
outdated DB2 version and the IFCID is no longer supported by OMEGAMON for Db2
Performance Expert, or the input data contains IFCIDs
from a newer DB2 version and OMEGAMON for DB2 PE is not yet aware of
If the job summary log shows message
FPEC4020I NUMBER OF RECORDS FROM UNSUPPORTED PRODUCT
RELEASES WAS ..., the input data (such as input data in DPMOUT format) was
created by earlier versions of OMEGAMON for Db2
Performance Expert or OMEGAMON for DB2 PM and is no
Identifying missing IFCIDs
Report sets such as Accounting, Locking, or Statistics require specific IFCIDs from DB2
instrumentation data. If the input data sets (specified with the INPUTDD statement in your job
stream) do not contain these IFCIDs, the generated report ends with
NO DATA TO
INPUT INPUT PROCESSED PROCESSED IFCID COUNT PCT OF TOTAL COUNT PCT OF TOTAL ------- ---------- ------------ ---------- ------------ 1 89 33.58% 0 0.00% 2 88 33.20% 0 0.00%
IFCIDcolumn or the
INPUT COUNTcolumn shows a count of 0, your input data does not contain this IFCID.
Reasons for missing IFCIDs
IFCIDs might be missing in your reports because they are either not collected (missing in the input data for the report generation) or being accidentally suppressed or filtered by inappropriate use of commands, subcommands, or subcommand options.
To identify why specific IFCIDs are not collected, review the methods of how the data was collected. For example, the DB2 startup parameters might determine that certain trace classes (with their implied IFCIDs) are not started.
- The GLOBAL command might apply global filters to all data serving as input to subsequent OMEGAMON for Db2 Performance Expert commands like ACCOUNTING or STATISTICS.
- OMEGAMON for Db2
Performance Expert commands like ACCOUNTING or STATISTICS
might use subcommand options that further restrict the data. The most
important ones are:
- FROM/TO might limit the time frame too much.
- INCLUDE/EXCLUDE might limit a Db2 trace class or an IFCID.
PROCESSED COUNTequals 0) during the report generation and consequently the Statistics report is empty.
INPUT INPUT PROCESSED IFCID COUNT PCT OF TOTAL COUNT ------- ---------- ------------ ---------- 1 48 25.00% 0 2 48 25.00% 0
Insufficient amount of Statistics record pairs (IFCIDs 1 and 2)
Output in a Statistics report requires at least two DB2 Statistics record pairs (IFCIDs 1 and 2) in the input data. These IFCIDs are collected at a configurable interval (Db2 system parameter STATIME).
An empty Statistics report usually indicates that either the input data does not cover at least two intervals or that filters restrict the amount of data being processed during report generation.
INPUT COUNTcolumn). However, filters have limited the number of processed records below the required minimum of two record pairs (
PROCESSED COUNTcolumn). Consequently, the Statistics report is empty.
INPUT INPUT PROCESSED PROCESSED IFCID COUNT PCT OF TOTAL COUNT PCT OF TOTAL ------- ---------- ------------ ---------- ------------ 1 48 25.00% 1 1.02% 2 48 25.00% 1 1.02%
STATISTICS REDUCE INTERVAL(60) BOUNDARY(60) REPORT FROM (12/22/13,12:15:00.00) TO (12/22/13,12:45:00.00)
Messages indicating incomplete Accounting data (IFCIDs 3 and 239)
NO DATA TO REPORT.
FPEA4531I GENERAL ACCOUNTING DATA FOR LUWID INSTANCE <V1> IS MISSING. IFCID 3 IS MISSING.
FPEA4532I ACCOUNTING DATA FOR A NUMBER OF PACKAGES FOR LUWID <V1> IS MISSING. ONE OR MORE IFCID 239 IS MISSING.
FPEA4534I COORDINATING PARALLEL TASK FOR LUW INSTANCE <V1> IS NOT REPORTED AS NOT ALL INFORMATION FOR ASSISTING PARALLEL TASKS FROM MEMBER <V1> IS AVAILABLE.
Accounting reports require IFCID 3 for reporting a thread. However, package or program data belonging to a thread is contained in multiple 239 IFCIDs. A 1:n relation is established within the data. For correct reporting a complete set of these IFCIDs is required in the input data.
In case of DB2 Query Parallelism, additional sets of IFCIDs 3 and 239 are required. They were created from parallel processors or from Db2 systems that assisted an initiating agent. Dependent on the degree of parallelism, this can result in a 1:p relation between agent and parallel tasks. In other words, correct Accounting processing needs from the agent one IFCID 3 and n IFCIDs 239, and for each of the p parallel tasks also one IFCID 3 and a certain number of IFCIDs 239.
Accounting processing needs a complete set of these IFCIDs for a correct reporting. If either IFCIDs 239 belonging to an IFCID 3 are missing, or if IFCIDs 239 are available but their IFCID 3 is missing, the entire thread is excluded from further processing and reporting.