IBM Support

IT18310: ADDITIONAL CALLS IN AGENT BREATHING POINT CAUSE POOR PERFORMANCEIN LOAD UTILITY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Excessive looping in Agent Breathing Point causes poor
    performance in the LOAD utility and may make the utility appear
    to hang.
    
    To identify, threads may be in this stack:
    0x0900000068096D0C sqldReadTemp__FP13SQLD_DFM_WORKl + 0x38C
    0x09000000677F8E94 @114@sqldFetchNext__FP13SQLD_DFM_WORK + 0x18
    0x0900000068312C24 sqldfrd__FP13SQLD_DFM_WORK + 0x1188
    0x0900000067971C74
    sqldRowFetch__FP8sqeAgentP8SQLD_CCBUlT3PP10SQLD_VALUEP8SQLZ_RIDT
    3P12SQLD_ID_LISTP9SQLP_LSN8 + 0x374
    0x09000000656E6284
    sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL
    Z_RIDPc@OL@23909 + 0x700
    0x090000006708ABF4
    sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL
    Z_RIDPc + 0xA4
    0x0900000066A5EDD4 sqluDMSortFetch__FPUcP4svalT1Pii + 0x80C
    
    and Trace timings will show that LOAD is in the INDEX BUILD
    phase.
    

Local fix

  • We can set DB2_ROWCOMP_TEMP=disable=util and it will avoid this
    area of looping.  Please keep in mind that setting this variable
    will make some changes in the internal compression used in
    utilities such as LOAD and REORG.  While their overall
    performance will be the same, setting this variable will mean
    that they require additional TEMP space.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 11.1 Fix Pack 2                               *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 11.1 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT18310

  • 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

    2016-12-08

  • Closed date

    2017-06-23

  • Last modified date

    2017-06-23

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
29 June 2020