IBM Support

PK61998: DYNAMIC SQL PROCESSING USING FAST APPLY USES TOO MUCH MEMORY WHEN A JOB IS RE-RUN WITH THE RESTART OPTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • The restart option allows dynamic SQL execution to begin
    processing at the statement following the last successful commit
    in the previous run after an error has occured. During a restart
    with Fast Apply, the amount of memory consumed to locate this
    restart point is roughly the same as the memory that was
    consumed executing all the SQL statements in the previous run
    before the error was encountered. This fix will reduce the
    memory needed to locate the restart point when using Fast Apply.
    
    MR1220075626
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: The restart option allows dynamic SQL   *
    *                      execution to begin processing at the    *
    *                      statement following the last successful *
    *                      commit in the previous run after an     *
    *                      error has occured. During a restart     *
    *                      with Fast Apply, the amount of memory   *
    *                      consumed to locate this restart point   *
    *                      is roughly the same as the memory that  *
    *                      was consumed executing all the SQL      *
    *                      statements in the previous run          *
    *                      before the error was encountered. This  *
    *                      fix will reduce the memory needed to    *
    *                      locate the restart point when using     *
    *                      Fast Apply. MR1220075626                *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

Temporary fix

Comments

  • APPLY the PTF.
    

APAR Information

  • APAR number

    PK61998

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    230

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2008-02-29

  • Closed date

    2008-03-28

  • Last modified date

    2008-05-05

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

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

Modules/Macros

  •    ALA#MREP
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R230 PSY UK35068

       UP08/04/07 P F804

  • R310 PSY UK35069

       UP08/04/04 P F804

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230"}]

Document Information

Modified date:
12 April 2021