IBM Support

PH59529: SUBSYSTEM CLONING DB2SCHEMA-UPDATE COMMAND DOES NOT DETECT SOME EXISTING TARGET SCHEMAS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In some cases, when checking for the existence of target schemas
    in a Db2 subsystem, the DB2SCHEMA-UPDATE command does not detect
    existing objects with target schemas. This might lead to
    subsequent errors from the Db2 CATMAINT utility.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 Cloning Tool for z/OS           *
    ****************************************************************
    * PROBLEM DESCRIPTION: In some cases, when checking for the    *
    *                      existence of target schemas in a Db2    *
    *                      subsystem, the DB2SCHEMA-UPDATE command *
    *                      does not detect existing objects with   *
    *                      target schemas. This might lead to      *
    *                      subsequent errors from the Db2 CATMAINT *
    *                      utility.                                *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    In some cases, when checking for the existence of target schemas
    in a Db2 subsystem, the DB2SCHEMA-UPDATE command does not detect
    existing objects with target schemas. This might lead to
    subsequent errors from the Db2 CATMAINT utility.
    

Problem conclusion

  • Apply the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH59529

  • 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

    2024-01-31

  • Closed date

    2024-02-07

  • Last modified date

    2024-03-03

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

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

Modules/Macros

  • CKZ00271 CKZ00281 CKZ00510 CKZ00540 CKZ00541 CKZ00543 CKZ00544
    CKZ00545 CKZ00547 CKZ00554 CKZ00555 CKZ00560 CKZ00562 CKZ00564
    CKZ00575 CKZ00613 CKZ00620 CKZ00621 CKZ00622 CKZ00624 CKZ00631
    CKZ00640 CKZ00670 CKZ00671 CKZ00674 CKZ00677 CKZ00708 CKZ00709
    CKZ00714 CKZ00716 CKZ00720 CKZ00721 CKZ00722 CKZ00723 CKZ00761
    CKZ00764 CKZ00765 CKZ00769 CKZ00780 CKZ00782 CKZ00984
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI95583

       UP24/02/08 P F402

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 April 2024