IBM Support

PI23046: DB2 ADMINISTRATION TOOL FOR Z/OS DURING CM RUN DOES CHECK DATA BEFORE REBUILD INDEX WHEN CREATING AN INDEX AND ADD CONSTRAINT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 Administration Tool for z/OS during CM RUN does CHECK DATA
    before REBUILD INDEX/REORG TS when CREATING an INDEX
    and adding CONSTRAINT(s) at the same time.
    .
    Additional info in the RUN job output: msgDSNU204I :
    .
    DSNU204I  ssid    timestamp   DSNUGDTC - PAGESET REBUILD
    PENDING ON INDEX schema.index_name PROHIBITS PROCESSING
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
    *                 z/OS who use Compare to run a POST utility   *
    *                 sequence when an index is in REBUILD         *
    *                 PENDING state and the table space is in      *
    *                 CHECK PENDING state.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Change Management (CM) RUN          *
    *                      function performs a CHECK DATA          *
    *                      before executing the REBUILD INDEX /    *
    *                      REORG TS utilities when creating        *
    *                      an INDEX and adding CONSTRAINT(s)       *
    *                      at the same time.  An informational     *
    *                      message DSNU204I / msgDSNU204I          *
    *                      is observed in the RUN job output:      *
    *                                                              *
    *                      DSNU204I  ssid    timestamp             *
    *                      DSNUGDTC - PAGESET REBUILD              *
    *                      PENDING ON INDEX schema.index_name      *
    *                      PROHIBITS PROCESSING                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After the compare, the changed DDL in the APPLY job or in the
    Work Statement List (WSL) may cause the DB2 object to be
    in a different Pending state and the post utility sequence
    will group together/execute the following sequence:
    
    1 - CHECK DATA
    2 - REBUILD INDEX
    3 - REORG TABLESPACE.
    
    to remove the Pending status.
    
    However, when the TABLE SPACE and INDEX are both in
    REORG PENDING, REBUILD PENDING and CHECK PENDING states,
    we need to run REORG to first remove the REORG PENDING
    state, then other post utility statements can be executed
    successfully.  When the TABLE SPACE and INDEX is not in
    REORG PENDING state (for example, ADVISORY REORG PENDING,
    REBUILD PENDING and CHECK PENDING), a REBUILD INDEX,
    CHECK DATA and REORG TS is needed to remove the pending
    state.
    
    Considering this situation and the post utility statements are
    grouped together after all changed DDL for all the DB2 objects,
    the correct post utility sequence should be:
    
    1 - REORG to remove the REORG PENDING state (phase
        1 REORG)
    2 - REBUILD INDEX
    3 - CHECK DATA
    4 - REORG for non-REORG (like ADVISORY REORG PENDING)
        PENDING state (phase 2 REORG)
    

Problem conclusion

  • The program has been changed to generate the following
    POST utility sequence :
    
    1 - REORG to remove the REORG PENDING state (phase
        1 reorg)
    2 - REBUILD INDEX
    3 - CHECK DATA
    4 - REORG for non-REORG (like ADVISORY REORG PENDING)
        PENDING state (phase 2 reorg)
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI23046

  • Reported component name

    DB2 OBJECT COMP

  • Reported component ID

    5697G6400

  • Reported release

    A20

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-01

  • Closed date

    2014-08-27

  • Last modified date

    2014-09-03

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

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

    UI20904 UI20905

Modules/Macros

  •    GOC5H
    

Fix information

  • Fixed component name

    DB2 OBJECT COMP

  • Fixed component ID

    5697G6400

Applicable component levels

  • RA20 PSY UI20904

       UP14/08/30 P F408

  • RB10 PSY UI20905

       UP14/08/30 P F408

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

Document Information

Modified date:
12 April 2021