IBM Support

PM57865: CKZ54767W INDEXSPACE MISMATCH ATTRIBUTE UNIQUERULE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Mismatch detection may occur when multiple indexes with
    different names that satisfy primary key and or unique rule
    constraints are present.  When cloning tool produces the DDL
    for these indexes, whichever index gets created first gets
    the UNIQUERULE P or C designation causing a mismatch detection.
    

Local fix

  • Create DB2 objects outside of DB2 Cloning Tool.
    .
    Steps to creating outside of DB Cloning Tool:
    
    1) Generate DDL from DB2 Admin Tool
    2) Edit the Generated DDL (Add a DROP DATABASE statement at
       the beginning of the generated DDL)
    3) Construct the DB2 Cloning Tool COPY statement to read and
       execute the external DDL dataset (Certain parameters are
       required to allow the DB2 Cloning Tool to read an external
       DDL dataset for input into the cloning process.
    4) Construct the DB2 Cloning Tool COPY statement to disable
       the process DDL parameter and create the cloned copies of
       the source data via ADRDSSU (Change the parameters in the
       DB2 Cloning Tool COPY statement in order to create the
       clone the target.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Mismatch detection may occur when       *
    *                      multiple indexes with different names   *
    *                      that satisfy primary key and or unique  *
    *                      rule constraints are present.  When     *
    *                      cloning tool produces the DDL for these *
    *                      indexes, whichever index gets created   *
    *                      first gets the UNIQUERULE P or C        *
    *                      designation causing a mismatch          *
    *                      detection.                              *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM57865

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-09

  • Closed date

    2012-02-27

  • Last modified date

    2012-04-03

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

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

Modules/Macros

  • CKZGASM2
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R310 PSY UK76584

       UP12/03/02 P F203

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.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021