IBM Support

PH61121: STORAGE LEAK WHEN CALLING A STORED PROCEDURE OR USER DEFINED FUNCTION 24/04/29 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With PH55497/UI93128 applied, storage leak happens when calling
    a stored procedure or user defined function that has static SQL
    statements that need to be incrementally bound. Possible symptom
    
    is ABEND04E RC00E2000C at DSNXEDP.DSNSVSVB OFFSET00A58.
    
    Additional keywords: ZSA1
    

Local fix

  • BYPASS/CIRCUMVENTION:
    N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Db2 13 for z/OS users who execute        *
    *                 stored procedures, user defined functions,   *
    *                 or triggers with PH55497/UI93128 applied.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: With PH55497/UI93128 applied, storage   *
    *                      leak happens for the following two      *
    *                      cases:                                  *
    *                      1. A stored procedure, user defined     *
    *                         function, or trigger has a static    *
    *                         DML statement invalidated by a DDL   *
    *                         statement in the same thread.        *
    *                         Storage leak happens when            *
    *                         the stored procedure, UDF, or        *
    *                         trigger is called in the same        *
    *                         thread again.                        *
    *                      2. With function level V13R1M504        *
    *                         activated, storage leak might        *
    *                         happen when executing an external    *
    *                         routine that is invalidated at a     *
    *                         statement level.                     *
    *                      The storage leak is in the local agent  *
    *                      pool. A possible symptom is ABEND04E    *
    *                      RC00E2000C at DSNXEDP.DSNSVSVB          *
    *                      OFFSET00A58.                            *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    With PH55497/UI93128 applied, storage leak happens for the
    following two cases:
    1. A stored procedure, user defined function, or trigger has a
       static DML statement invalidated by a DDL statement in the
       same thread. Storage leak happens when the stored procedure,
       UDF, or trigger is called in the same thread again. In this
       case the invalidated DML statement need to go through
       incremental bind.
    2. With function level V13R1M504 activated, storage leak might
       happen when executing an external routine that is
       invalidated at a statement level. The invalid DML statements
       need to go through incremental bind before autobind phase-in
       of the package finishes.
    The storage leak is in the local agent pool. A possible symptom
    is ABEND04E RC00E2000C at DSNXEDP.DSNSVSVB OFFSET00A58 when
    storage leak is accumulated.
    
    Additional keywords:
    DB2STGLK/K SQLSP SQLSTOREDPROC SQLNATIVESQLPL SQLUDF
    SQLTABLEUDF SQLTRIGGER
    

Problem conclusion

  • Db2 code that saves and restores environment when executing a
    nested level (routine, trigger) has been changed to reuse the
    same storage needed for increment bind of an invalidated
    statement.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH61121

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    D10

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-29

  • Closed date

    2024-05-23

  • Last modified date

    2024-06-03

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

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

    UI97035

Modules/Macros

  • DSNXESTR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RD10 PSY UI97035

       UP24/05/31 P F405 {

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D10","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 June 2024