Re: Performance impact of SQL monitors

On 24-Apr-2015 08:32 -0500, rob wrote:

Coworker used SQL Performance Monitor Wizard from IBM Navigator.
Three boxes were checked:
Job name (and job name was supplied)
Job user (and job user was supplied)
Statements that access these objects (and one view in one schema was
supplied). <<SNIP>>

Were the impacted jobs reviewed for errors logged in the joblog? If the monitoring is /stumbling/ while logging, then of course purposefully any difficulties encountered should not cause the SQL to fail. Yet any /trip-ups/ may be manifest as excessive exception processing and handling; work other than successful logging, that would add to the overall wall-clock time taken to perform just the SQL work with logging.

The latest apparent fix for the DB Monitor feature appears to be the following PTF; including changes related to the filtering choices, although nothing specifically PERFM related in the list of superseded PTFs, yet their obfuscation by labeling most of those earlier changes as /internal maintenance/ could be corrective for just about anything:
<http://www-912.ibm.com/a_dir/as4ptf.nsf/ALLPTFS/SI55327>