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 .

Usage examples


This section describes a few of the possible uses of application traces. Its purpose is to help you discover how to use a trace to solve unique problems.

Application trace allows the following functions:

  • Testing by application developers of application correctness and performance
  • Review of SQL by database administrators before accepting it for production use
  • Analysis of I/O by page set (table spaces and index spaces) by database administrators
  • Periodic performance reviews of specific application groups
  • Investigation of a specific plan suspected of poor performance (or identified in previous summary analysis)
  • Analysis of index usage and database access paths (scans) and I/O and lock request patterns as necessary
  • Traces of ad hoc SQL usage to find users that need training in SQL concepts to improve performance
  • Ad hoc analysis of workload history for a Db2 system
  • Checks of the performance characteristics of a new application that is accessing production databases
  • Ongoing exception traces per workload type to be set up to detect bad applications that do not meet performance criteria or service levels or affect total system performance

This section contains the following topics:



 

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