PI05901: WHEN INCREMENTEVENT IS "NO", CORRELATIONS CAN BE CREATED FOR SQL STATEMENT EXECUTIONS THAT OCCUR AT DIFFERENT TIMES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The correlations do not take into account the timestamps of the
  alerts, so, if the same SQL statement generates alert during
  more than one execution, all getpage alerts from all executions
  will correlatewith all cpu alerts from all executions (for
  example).
  When incrementEvent is "yes", there will only be one alert of
  each type for a given SQL statement, regardless of the number of
  executions that generate alerts. In this case there will be only
  one correlation, so the correlations are only a problem for the
  incrementEvent = "no" case.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Query Monitor.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: The correlations do not take into       *
  *                      account the timestamps of the alerts,   *
  *                      so, if the same SQL statement generates *
  *                      alert during more than one execution,   *
  *                      all getpage alerts from all executions  *
  *                      will correlatewith all cpu alerts from  *
  *                      all executions (for example). When      *
  *                      incrementEvent is "yes", there will     *
  *                      only be one alert of each type for a    *
  *                      given SQL statement, regardless of the  *
  *                      number of executions that generate      *
  *                      alerts. In this case there will be only *
  *                      one correlation, so the correlations    *
  *                      are only a problem for the              *
  *                      incrementEvent = "no" case.             *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• CQMMACTX
  

Fix information

• Fixed component name

  DB2 QUERY MONIT

• Fixed component ID

  5655E6701

Applicable component levels

• R310 PSY UI14047

     UP14/01/23 P F401

• R320 PSY UI14048

     UP14/01/23 P F401

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.