IBM Support

LI74451: LOAD WITH CLIENT OPTION (OR CLI LOAD) THAT IS INTERRUPTED MAY TRAP WITH SQLODIAGNOSEFREEBLOCKFAILURE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When the Load utility is invoked from a remotely connected
    client and the CLIENT option is specified (meaning data is being
    retrieved from the client), or the CLI Load interface is used,
    if the utility is interrupted or fails, it's possible in some
    timing situations that the Load Agent process drives a rollback
    and free's resources before all of it's child processes have
    exited, causing the Load to trap with errors such as this:
    
    2009-04-07-15.32.51.513504-240 I4089969E2013       LEVEL: Severe
    PID     : 12699                TID  : 208729532768 PROC :
    db2sysc 0
    INSTANCE: xxx             NODE : 000          DB   :xxx
    
    APPHDL  : 0-38628              APPID:P00000.D289.004E97180854
    AUTHID  : Kxxxx
    EDUID   : 3479                 EDUNAME: db2lfrm0 0
    FUNCTION: DB2 UDB, SQO Memory Management,
    sqloDiagnoseFreeBlockFailure, probe:60
    MESSAGE : The associated pool has already been freed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When the Load utility is invoked from a remotely connected   *
    *                                                              *
    * client and the CLIENT option is specified (meaning data is   *
    * being                                                        *
    * retrieved from the client), or the CLI Load interface is     *
    * used,                                                        *
    * if the utility is interrupted or fails, it's possible in     *
    * some                                                         *
    * timing situations that the Load Agent process drives a       *
    * rollback                                                     *
    * and free's resources before all of it's child processes have *
    *                                                              *
    * exited, causing the Load to trap with errors such as this:   *
    *                                                              *
    *                                                              *
    *                                                              *
    * 2009-04-07-15.32.51.513504-240 I4089969E2013      LEVEL:     *
    * Severe                                                       *
    * PID    : 12699                TID  : 208729532768 PROC :     *
    *                                                              *
    * db2sysc 0                                                    *
    *                                                              *
    * INSTANCE: xxx            NODE : 000          DB  :xxx        *
    *                                                              *
    *                                                              *
    * APPHDL  : 0-38628                                            *
    * APPID:P00000.D289.004E97180854                               *
    * AUTHID  : Kxxxx                                              *
    *                                                              *
    * EDUID  : 3479                EDUNAME: db2lfrm0 0             *
    *                                                              *
    * FUNCTION: DB2 UDB, SQO Memory Management,                    *
    *                                                              *
    * sqloDiagnoseFreeBlockFailure, probe:60                       *
    *                                                              *
    * MESSAGE : The associated pool has already been freed.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * upgrade to v91fp10                                           *
    ****************************************************************
    Closing APAR as- planned to be fixed in next Release.
    

Problem conclusion

  • fix contained in v91fp10
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI74451

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-21

  • Closed date

    2011-07-14

  • Last modified date

    2011-07-14

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

    LI74450

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

Fix information

Applicable component levels

  • R910 PSY

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

Document Information

Modified date:
17 October 2021