IBM Support

PM70181: PERFORMANCE ENHANCEMENT FOR THE RECOVER WITH BACKOUT YES UTILITY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • RECOVER with BACKOUT YES utility needs improved performance
    during the LOGUNDO phase.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users of RECOVER BACKOUT YES         *
    *                 Utility.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: PERFORMANCE ENHANCEMENT FOR THE RECOVER *
    *                      WITH BACKOUT YES UTILITY.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Today, LOG UNDO phase of the RECOVER utility with BACKOUT YES,
    periodically commits the data changes. This commit was intended
    to restart the utility, in case of log apply failure during UNDO
    phase. However, today, restart of the RECOVER BACKOUT YES is not
    supported. i.e. if RECOVER BACKOUT YES fails in any phase, it
    must be restarted from the beginning. Therefore, periodic commit
    serves no purpose. The cost of periodic commit is high since it
    involves forcing out data changes to DASD. This write I/Os are
    expensive. This APAR will avoid performing periodic commits
    during LOG UNDO phase which may significantly improve the
    performance of UNDO phase.
    

Problem conclusion

  • DB2 logic of RECOVER utility with BACKOUT YES option is modified
    to improve the performance of LOG UNDO phase which in turns
    improves the over all performance of RECOVER BACKOUT YES
    utility.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM70181

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-02

  • Closed date

    2012-09-11

  • Last modified date

    2012-10-01

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

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

    UK81719

Modules/Macros

  • DSNIUNDO
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK81719

       UP12/09/26 P F209

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 October 2012