IBM Support

IT21593: INGEST MAY USE EXCESSIVE AMOUNT FOR OVERFLOW MEMORY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • INGEST uses approximately SHM_MAX_SIZE of base memory, plus it
    may use a varying amount of overflow memory.
    
    There is no limit to the amount of overflow memory, and in
    some scenarios we are using excessive amount overflow memory
    and it may impact system resources.
    
    INGEST client db2diag.log may have below message:
    -----
    2017-05-10-01.02.53.069040+540 I3326440A717         LEVEL:
    Warning
    PID     : 13566156             TID : 258            PROC : db2bp
    
    INSTANCE: db2inst1             NODE : 000
    HOSTNAME: DB2INST1
    EDUID   : 258
    FUNCTION: DB2 UDB, Ingest utility,
    SqludiFieldSetOverflowMemory::sqludiFreeAllFieldSetOverflowBlock
    s,
    probe:10
    DATA #1 : String, 282 bytes
    During the ingest operation, in order to improve performance or
    to
    avoid a
    deadlock, the utility needed to allocate additional memory.
    This can be
    avoided by increasing the value of ingest configuration
    parameter
    shm_max_size by the number of bytes indicated by data item #2
    below.
    DATA #2 : unsigned integer, 8 bytes
    38386936936
    DATA #3 : unsigned integer, 8 bytes
    24
    -----
    

Local fix

  • No workaround available.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Db2 Version 11.1                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 Version 11.1 Mod 3 Fix Pack 3.                *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Db2 Version 11.1 Mod 3 Fix Pack 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21593

  • 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

    2017-07-26

  • Closed date

    2018-03-16

  • Last modified date

    2018-03-16

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

    IT20886

  • 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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 March 2018