IBM Support

IC69449: ERROR SQL0954C DOING CLI LOAD OF LOB OR LONG COLUMNS BECAUSE OF HIGH APPLICATION HEAP MEMORY USAGE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When doing a CLI LOAD of columns of LONG or LOB data types,
    application heap memory usage grows so that you might get error:
     SQL0954C Not enough storage is available in the application
    heap to process the statement.
    
    If you get the error, db2diag.log contains an entry like this:
    
     9999-12-31-00.00.00.000000+000 XXXXXXXXXXXX       LEVEL: Severe
     PID     : XXXXX                TID  : XXXXXXXXXXXXXXXX :
    db2agent (XXXXXXXX) 0
     INSTANCE: XXXXXXXX             NODE : 000         DB
    :XXXXXXXX
     APPHDL  : XXXXX
    APPID:XXXXXXXXXXXXXXXXXXXXXXXXXX
     AUTHID  : XXXXXXXX
     FUNCTION: DB2 UDB, relation data serv, sqlrr_array_input_load,
    probe:95
     RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH
               "No memory available in 'Application Heap'"
               DIA8301C No memory available in the application heap.
    

Local fix

  • As a workaround, increase the database configuration parameter
    APPLHEAPSZ.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of DB2 for Linux, UNIX and Windows                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * .                                                            *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.1 Fix Pack 10.
    At a minimum, this fix should be applied on the database
    
    server.
    

Temporary fix

  • As a workaround, you can set the database configuration
    
    parameter APPLHEAPSZ to AUTOMATIC or increase its value.
    

Comments

APAR Information

  • APAR number

    IC69449

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-24

  • Closed date

    2011-06-20

  • Last modified date

    2011-06-20

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

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

    IC69689 IC69691 IC71922

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R910 PSN

       UP

  • R950 PSN

       UP

  • R970 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"9.1"}]

Document Information

Modified date:
16 September 2021