IBM Support

PM67774: EXTENDED INSIGHT OVERHEAD HIGH

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • With V10, DB2 introduced Monitor trace class 29 which activates
    these flag IFCIDs 318 and 400, but is also activates the new DB2
    function to externalize / write the SQL evicted from the SQL
    caches to the destination used in the START TRACE command. This
    is the additional SMF output which customers will experience.
    

Local fix

  • If Extended Insight is configured via ICAT or PARMGEN  the flag
    IFCID 318 (and 400 in case of DB2 10) has to be started in order
    to have the SQL (dyn & static) statement cache(s) populated with
    performance metrics.
    =>  Flag IFCIDs do not usually produce any trace record output,
    neither to OP buffer nor to SMF.
    
    DB2 introduced now  with V10 the Monitor trace class 29 which
    activates these flag IFCIDs 318 and 400, but is also activates
    now the new DB2 function to externalizes / write the SQL evicted
    from the  SQL caches to the destination used in the START TRACE
    command. This is the additional SMF output which the customer
    is experiencing.
    
    There are two work around for the time being to stop MON
    Class(29) but start the flag IFCIDs 318 and in case of DB2 10
    the flag IFCID 400 .
    
    1. Specify in ICAT Monitor profile definition panel "A  Start
       additional DB2 traces  "
    
    KD2PTRAC OMEGAMON XE for DB2 PE - Start additional DB2 traces-
    PROFID:
    TEST
    Command ===>
     Start the following DB2 traces:
       DB2 command 1:
        IFCID 318 (Dynamic SQL statement cache) ==> Y  (Y, N)
        IFCID 400 (Static SQL statement cache)  ==> Y  (Y, N)
        Command   ==> START TRACE(MON) CLASS(29) DEST(SMF)
       DB2 command 2: STOP  TRACE(MON) CLASS(29)
    DEST(SMF)______________
       DB2 command 3: START TRACE(MON) CLASS(1) DEST(SMF)
    IFCID(318,400)
       DB2 command 4:
     Enter=Next  F1=Help  F3=Back
       then "Create Profile Members" and "Create runtime members
    (DB2
    related)" which will update the hlq.RKD2PAR(OMPEssid)
    
    2. The quick but temporary solution would be to edit the
       generated hlq.RKD2PAR(OMPEssid) and exchange manually the
       parameter DB2COMMAND='START TRACE(MON) CLASS(29) DEST(SMF)'
       with
       DB2COMMAND='START TRACE(MON) CLASS(1) DEST(SMF) IFCID(318,400
       )'
       But be aware that with the next ICAT change and re-creation
       of the RTE members the manual edit OPMEssid member will be
       overwritten, therefore the alternative 1) is the recommended
       one.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   ICAT                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Currently for E2E trace class 29 is     *
    *                      started when OMPE collector starts up.  *
    *                      This class may collect data that is     *
    *                      not required for E2E and therefore may  *
    *                      produce overhead in data collection.    *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    *                                                              *
    ****************************************************************
    PROBLEM SUMMARY:
    For E2E data collection trace class 29 is used because it
    contains data from IFCIDs 318 and 400. There is further
    information collected with this trace class that is not required
    for E2E. For this the configuration needs to be changed to
    use only IFCIDs 318 and 400 instead of trace class 29.
    
    PROBLEM CONCLUSION:
    The data collection for E2E now uses only IFCIDs 318 and 400
    instead of trace class 29.
    

Problem conclusion

Temporary fix

Comments

  • The data collection for E2E now uses only IFCIDs 318 and 400
    instead of trace class 29.
    
    KEYWORDS : E2E IFCID 318 400 CLASS 29
    

APAR Information

  • APAR number

    PM67774

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    510

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-27

  • Closed date

    2012-08-13

  • Last modified date

    2012-09-05

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

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

    UK81043

Modules/Macros

  • KD2CRPLC KD2HTRC  KD2HTRCA KD2HTRCB KD2HTRCC
    KD2PTRAC KD261SB2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R510 PSY UK81043

       UP12/08/16 P F208

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 September 2012