IBM Support

PK59452: WRONG TARGET INDEX IS MAPPED TO A SOURCE INDEX. IN THIS CASE, THE COLCOUNTS ARE DIFFERENT, LEADS TO MSGCKZ54763W

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem is the wrong target index is mapped to a source
    index. In this case, the COLCOUNTS are different and thus the
    message...CKZ54763W INDEXSPACE Mismatch, Attribute COLCOUNT,
    etc.
    When a database (DB) or indexspace (IS) object translate command
    is present for an index, the DB.IS is used first to read the
    target index object. In this case only the DB object translate
    was specified and the indexspace happened to exist for this
    index but did not match the correct source indexspace name.
    

Local fix

  • When matching indexspace names appear on different objects from
    source to target, use an indexspace object translation command
    to map the correct source indexspace name to the target
    indexspace name. You need as many indexspace object translations
    as there are incorrectly matching DB.IS object pairs.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 cloning tool.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The problem is the wrong target index   *
    *                      is mapped to a source index. In this    *
    *                      case, the COLCOUNTS are different and   *
    *                      thus the message...CKZ54763W INDEXSPACE *
    *                      Mismatch, Attribute COLCOUNT, etc. When *
    *                      a database (DB) or indexspace (IS)      *
    *                      object translate command is present for *
    *                      an index, the DB.IS is used first to    *
    *                      read the target index object. In this   *
    *                      case only the DB object translate was   *
    *                      specified and the indexspace happened   *
    *                      to exist for this index but did not     *
    *                      match the correct source indexspace     *
    *                      name.                                   *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK59452

  • Reported component name

    DB2 CLONING TOO

  • Reported component ID

    5655N1000

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-01-16

  • Closed date

    2008-02-20

  • Last modified date

    2008-03-03

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

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

Modules/Macros

  •    CKZ00780
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R210 PSY UK33889

       UP08/03/03 P F802

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

Document Information

Modified date:
03 March 2008