Configuring additional Db2 traces

You can configure and start additional Db2 traces.

About this task

For certain functionality, such as displaying SQL statements and metrics for dynamic statement cache or EDM pool, it is required to start additional Db2 traces. Starting these traces can cause considerable CPU overhead. Therefore, these traces are not started by default. With this option you can specify if additional Db2 traces should be started automatically when the OMEGAMON® Collector starts.

Procedure

There are two options available for configuring additional Db2 traces. Select one of the following options:

Set parameter KD2_PFxx_TRACES_318 and parameter KD2_PFxx_TRACES_400 to Y. This enables collection IFCID 318 for dynamic and IFCID 400 for static statement cache metrics.

Use the KD2_PFxx_TRACES_DB2CMDx parameters (where x is either 2, 3, or 4). This option enables you to provide three more custom START TRACE commands. Since it is not possible to add line breaks to the statement, use abbreviations for this command wherever possible.