IBM Support

PI94675: TREAT SQLCODE = 162 AS A WARNING AND NOT AS AN ERROR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer has encountered a situation where the DDL generator
    added a referential constraint to an already existing and
    populated child table. Execution of this statement resulted in
    SQLCODE=162 (TABLE table name HAS BEEN PLACED IN CHECK PENDING).
    While this situation can indicate possible problems with cloned
    objects, it should not be treated as error.
    

Local fix

  • Drop child table on target Db2 and clone it from source Db2
    along with its parent table.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM Db2 Cloning Tool z/OS.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Customer has encountered a situation    *
    *                      where the DDL generator added a         *
    *                      referential constraint to an already    *
    *                      existing and populated child table.     *
    *                      Execution of this statement resulted    *
    *                      in SQLCODE=162 (TABLE table name HAS    *
    *                      BEEN PLACED IN CHECK PENDING). While    *
    *                      this situation can indicate possible    *
    *                      problems with cloned objects, it        *
    *                      should not be treated as error.         *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI94675

  • 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

    2018-03-05

  • Closed date

    2018-04-23

  • Last modified date

    2018-05-01

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

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

Modules/Macros

  •    CKZBTS
    

Fix information

  • Fixed component name

    DB2 CLONING TOO

  • Fixed component ID

    5655N1000

Applicable component levels

  • R320 PSY UI55393

       UP18/04/25 P F804

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

Document Information

Modified date:
31 March 2021