Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Db2 13.1 image-2024-5-19_8-5-1.png .

Introduction to Performance Reporter

Many Db2 performance problems cannot be recognized by obvious real-time symptoms (for example, loops and exceptions).

Often, a detailed analysis is required, using data that is obtained over long periods of time. In cases where a large volume of data needs to be analyzed, a printed report is easier to read than an online report that requires scrolling through many screens. BMC AMI Ops Monitor for Db2 addresses this situation by providing the ability to produce printed reports either from Db2 IFCIDs or from data previously loaded into Db2 tables for long-term tracking.

Related topic

Using-Performance-Reporter

Performance Reporter is an offline analysis system that produces reports and plots that can be used to evaluate Db2 system and application performance. These evaluations can be used for Db2 planning, forecasting, and performance management.

The input data to Performance Reporter are Db2 trace records (IFCIDs). Performance Reporter processes accounting, statistics, and audit records. The data source can be the records written by Db2 to SMF, or records written to MVDB2/DC trace data sets and copied to sequential files in SMF format through an archiving process. For more information about defining trace data sets, specifying which IFCIDs should be collected, and setting up the archive process, see Using-the-application-trace-facility and the BMC AMI SQL Performance for Db2 documentation.

BMC Software recommends using the Data Collector reports. In special cases, when a report of recent activity is needed, the Data Collector reports can be produced from active trace logs. In this case, the Data Collector address space must be active.

The trace records can also be loaded into Db2 tables where the power of Structured Query Language (SQL) can be used to fulfill your reporting needs. Queries that are distributed with the product or modified/developed on-site can be used to generate reports. Data summarization and purge routines can be used to control the amount of data while still allowing for both short- and long-term historical reporting. Of special importance is the ability to summarize accounting records before the table load process, reducing both processing overhead and disk storage requirements for the tables.

Important

Reports on detail performance trace records (SQL and so on) are processed as part of the Application Trace batch trace print facility, from trace logs or in some cases from SMF data. (For more information, see Printing-trace-log-data-sets.) Also, some system event trace records captured by the Data Collector are available in BMC AMI OpsM for Db2 views. You can use the EXPORT command or the BMC AMI Ops Batch utility to produce printed reports from these views.

The following figure summarizes the processing flow used to produce these reports and charts with Performance Reporter.

GUID-E4B25200-34F5-45C7-83EF-4F5F1465CE6C-low.png

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*