IBM Support

PH42195: ADD START DB RW PRIOR TO REORG IN WSL TO MAKE TABLES AVAILABLE SOONER AFTER CHANGES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When changes are applied to a tablespace or table, DB2 Admin
    Tool issues a STA DB with RO command, applies the changes,
    performs a REORG and then starts the database again with access
    RW. This causes the table to be unavailable for updates for an
    unnecessarily long time, particularly in the case of big tables.
    The database should be started first with RW access before
    performing the REORG with SHRLEVEL CHANGE.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 Administration Tool for z/OS    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using Change Management (CM) to    *
    *                      alter a table on which you must run the *
    *                      REORG utility to clear pending states,  *
    *                      the generated job does not set the      *
    *                      table space to read-write (RW) status   *
    *                      until after the REORG operation         *
    *                      completes. REORG could run for a long   *
    *                      time and leave the table in read-only   *
    *                      (RO) status for all that time.          *
    *                      Also, the generated job includes a      *
    *                      second unnecessary START DB command at  *
    *                      the end of the job.                     *
    ****************************************************************
    The customer is using CM to alter a table and wants to clear the
    pending states by running REORG.  However, the job that is
    created to perform this operation leaves the table in RO status
    while REORG is processing and the table cannot be updated for
    potentially a long time.  The table space should be started with
    RW status before REORG completes.  Also, a second START DB
    ACCESS(RW) command is included at the end of the job and is not
    needed.
    

Problem conclusion

  • The problems have been resolved.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH42195

  • Reported component name

    DB2 ADMIN TOOL

  • Reported component ID

    568851500

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-18

  • Closed date

    2022-02-14

  • Last modified date

    2022-03-01

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

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

    UI79302

Modules/Macros

  • ADBGAJOB
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • RC10 PSY UI79302

       UP22/02/17 P F202

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":"12.1.0"}]

Document Information

Modified date:
02 March 2022