IBM Support

PK15499: HIGH CPU USAGE BY QUERY MONITOR COLLECTOR TASK WHEN ENCOUNTERINGLONG-RUNNING UNIT-OF-WORK. POTENTIAL LOOP OR HANG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Code is being modified to eliminate potential high CPU usage by
    the Query Monitor collector started task when long-running units
    of work are encountered.
    
    *********************
    ALSO ADDRESSED IN THIS PTF UK10357
    **********************
    POTENTIAL LOOP DURING QM SHUTDOWN PROCESS WHEN SYSTEM SQL
    ACTIVITY IS HIGH.
    *
    If QM is ordered to shut down during a time of high SQL
    activity, it is possible for QM to go into a loop.  Code has
    been modified to eliminate this loop and allow QM to shut down
    normally.  Additional symptom:  Possible loop in CQMMMETR.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Code is being modified to eliminate     *
    *                      potential high CPU usage by the Query   *
    *                      Monitor collector started task when     *
    *                      long-running units of work are          *
    *                      encountered.                            *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK15499

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2005-11-18

  • Closed date

    2005-12-21

  • Last modified date

    2006-07-25

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

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

    UK10357

Modules/Macros

  •    CQM#INTV CQMMALRT CQMMCMDS CQMMESQL CQMMEXCP
    CQMMEXCW CQMMINDB CQMMMETR CQMMSCLN CQMMSQLW CQMMSSQL CQMMSTRM
    CQMTTEXT CQMTTXTW H238210J
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R210 PSY UK10357

       UP06/01/12 P F601

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
22 August 2024