The performance trace provides information about various DB2 events, including those related to distributed data processing. You can use this information to identify a suspected problem or to tune DB2 programs and resources for individual users or for DB2 as a whole. To start a performance trace, you must use the –START TRACE(PERFM) command. Performance traces cannot be automatically started. Performance traces are expensive to run, and consume much CPU. They also collect a large volume of information. Performance traces are usually run using an online monitor tool, or the output from the performance trace can be sent to SMF and then analyzed using a monitor reporting tool, or sent to IBM for analysis.
Because performance traces can consume numerous resources and generate numerous data, you have many options when starting the trace to balance the information that is desired with the resources consumed. These options include limiting the trace data that is collected by plan, package, trace class, and even IFCID.
Performance traces are typically used by online monitor tools to track a specific problem for a given plan or package. Reports can then be produced by the monitor software, and can detail SQL performance, locking, and many other detailed activities. Performance trace data can also be written to SMF records, and batch reporting tools can read those records to produce detailed information about the execution of SQL statements in the application.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|