Skip to Content

Default language.

Use exception filters on detail traces

Using exception filters, such as TIMEOUT > 1, in a detail trace is much more complex than in a summary trace.

These filters can only be checked when the accounting record is received, but in the meantime the event records must be collected and managed. Then, when the thread is completed, the exception conditions can be checked and the decision made whether to keep the collected data or discard it.

Because only completed threads are shown on the CT view, only threads that meet the filter conditions will be shown. Depending on the number of threads traced, the number of events traced, and the size of the online viewing STORAGE buffer, all events per thread might not be available; however, the events that are available might provide a sufficient amount of data.

Related topic

Recommendations-for-detail-traces-of-long-running-threads

If the trace is logged, INCMP entries are created for a thread whenever a buffer fills up and some of the detail events must be written to a log. When the accounting record is received, but does not match the filter criteria, the INCMP entry for that thread remains, because it controls the detail events that are already on the log. If the accounting record is never received (a long-running thread), or a log switch occurs before it is received, these INCMP entries also remain. Only view complete threads. In this case, all INCMP entries should be ignored as non-matches.


 

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

BMC AMI Ops Monitor for Db2 13.1