IBM Support

IT28616: pureScale - MON_GET_PKG_CACHE_STMT causes several sqleSubRequestRouter and sqlkdReceiveData probes messages in db2diag.log.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • We have a query calling MON_GET_PKG_CACHE_STMT  (with the member
    parameter set to "-2" so that request is sent to all nodes).
    Moreover, that query also specifies "FETCH FIRST 1 ROWS ONLY" so
    that the query is satisfied when 1 row is returned.   Since "-2"
    was specified the MON_GET_PKG_CACHE_STMT request is sent to all
    nodes.   The local node returns its data and the table function
    closes due to the "FETCH FIRST 1 ROWS ONLY".  In addition the
    app issuing this query immediately terminates; this termination
    results in a "STOP USING" interrupt being sent to all nodes.
    On a remote node by the time the app is initialized and the
    MON_GET request is passed to a subagent the STOP USING interrupt
    has arrived.   The arrival of that interrupt is detected and the
    probes are written out and the MON_GET request is aborted.
    This is highly timing sensitive; it only occurs if the STOP
    USING interrupt arrives before the subagent receives the MON_GET
    request for processing.  This scenario keeps repeating as DMS
    keeps running the query in the manner described above.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28616

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-29

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022