IBM Support

PH16019: INTEGRITY CONSTRAINT VIOLATION WHEN CLEANING UP GHOSTED ENVIRONMENT RECORDS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • As part of deployment history cleanup, ghosted environments
    without active references are purged from the database.
    
    Under certain conditions, environments will fail to delete due
    to the following exception:
    java.sql.SQLException: ORA-02292: integrity constraint
    (PIBMUCD.DS_CMP_2_VER_CREATION_ENV_ID) violated - child record
    found
    
    This is caused when a component is configured to run an
    application process on a ghosted environment whenever a new
    version is imported into that component.
    

Local fix

  • Navigate to the configuration page for the component which is
    referencing the environment, and change the configuration so it
    no longer references the environment.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * As part of deployment history cleanup, ghosted environments  *
    * without active references are purged from the database.      *
    *                                                              *
    * Under certain conditions, environments will fail to delete   *
    * due                                                          *
    * to the following exception:                                  *
    * java.sql.SQLException: ORA-02292: integrity constraint       *
    * (PIBMUCD.DS_CMP_2_VER_CREATION_ENV_ID) violated - child      *
    * record                                                       *
    * found                                                        *
    *                                                              *
    * This is caused when a component is configured to run an      *
    * application process on a ghosted environment whenever a new  *
    * version is imported into that component.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 7.0.4.2                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 7.0.4.2
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH16019

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    626

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-23

  • Closed date

    2019-12-03

  • Last modified date

    2019-12-03

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

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

Fix information

  • Fixed component name

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"626","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 December 2019