IBM Support

PI75533: REBUILD INDEX ENHANCEMENTS / RFE74185

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This enhancement to Dynamic Rebuild
    (keyword  REBUILD-INDEXES-EXECUTE ( Y ) )  includes several new
    keywords that offer more flexibility and more efficient resource
    utilization when Rebuild Index is required at the end of the
    clone.
    With these new keywords:
    .
    - A single Rebuild statement is generated per tablespace,
     including all indexes or index partitions that require rebuild,
     in order to maximize the efficiency of Rebuild by reading the
     table just once and using automatic multi-tasking to rebuild
     the indexes or index partitions.
    .
    - Source-only indexes may be excluded even when
     ALWAYS-COPY-INDEXSPACES ( Y ) is used, removing a prior
     limitation.
    .
    - Target-only or "unmatched" indexes can be included in the
     single Rebuild statement.
    .
    - A JCL version of the Rebuild stream is written to an optional
     CKZINTRB DD, if supplied on the Target job, should a restart be
     required.
    .
    - An optional report describes which indexes or index partitions
     are rebuilt, grouped by tablespace (this report can also be
     requested even when the new type of rebuild processing is not
     specified, as a type of "preview" functionality).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: This enhancement to Dynamic Rebuild     *
    *                      (keyword  REBUILD-INDEXES-EXECUTE       *
    *                      ( Y ) )  includes several new           *
    *                      keywords that offer more flexibility    *
    *                      and more efficient resource utilization *
    *                      when Rebuild Index is required at the   *
    *                      end of the clone.                       *
    *                      With these new keywords:                *
    *                      - A single Rebuild statement is         *
    *                       generated per tablespace, including    *
    *                       all indexes or index partitions that   *
    *                       require rebuild, in order to maximize  *
    *                       the efficiency of Rebuild by reading   *
    *                       the table just once and using          *
    *                       automatic multi-tasking to rebuild     *
    *                       the indexes or index partitions.       *
    *                      - Source-only indexes may be excluded   *
    *                       even when                              *
    *                       ALWAYS-COPY-INDEXSPACES ( Y ) is used, *
    *                       removing a prior limitation.           *
    *                      - Target-only or "unmatched" indexes    *
    *                       can be included in the                 *
    *                       single Rebuild statement.              *
    *                      - A JCL version of the Rebuild stream   *
    *                       is written to an optional CKZINTRB DD, *
    *                       if supplied on the Target job, should  *
    *                       a restart be required.                 *
    *                      - An optional report describes which    *
    *                       indexes or index partitions are        *
    *                       rebuilt, grouped by tablespace (this   *
    *                       report can also be requested even      *
    *                       when the new type of rebuild           *
    *                       processing is not  specified, as a     *
    *                       type of "preview" functionality).      *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI75533

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-26

  • Closed date

    2017-04-17

  • Last modified date

    2017-05-01

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

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

Modules/Macros

  •    CKZ2MAIN
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI46483

       UP17/04/24 P F704

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":"SSAUUE","label":"IBM Db2 Cloning Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 May 2017