kfogarty.com – Database Consultants

Website of Kenny Fogarty. An independent database consultant, based in London, England.

Monitor Trace

Filed under: DB2, Traces — Kenny at 12:52 am on Monday, September 18, 2006

An amalgamation of useful performance monitoring information is recorded by the DB2 monitor trace. Most of the information is also provided by other types of DB2 traces. The primary reason for the existence of the monitor trace type is to enable you to write application programs that provide online monitoring of DB2 performance.

Information provided by the monitor trace includes the following:

  • DB2 statistics trace information
  • DB2 accounting trace information
  • Information about current SQL statements

Estimated overhead

The overhead that results from the monitor trace depends on how it is used at your site. If, as recommended, class 1 is always active, and classes 2 and 3 are started and stopped as required, the overhead is minimal (approximately 2 to 5 percent, depending on the activity of the DB2 system and the number of times that the other classes are started and stopped). However, if your installation makes use of the reserved classes (30 through 32) or additional classes (as some vendors do), your site will incur additional overhead.

Sphere: Related Content

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.