PH16019: INTEGRITY CONSTRAINT VIOLATION WHEN CLEANING UP GHOSTED ENVIRONMENT RECORDS

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 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