PI64976: UNABLE TO DELETE BUILD LIVES WHEN USING MYSQL 5.7+ AS DATABASE

IBM UrbanCode Build Fix Pack 2 (6.1.2.3) for 6.1.2

APAR status

• Closed as program error.

Error description

• Due to a change in the way "ON DELETE CASCADE" works in more
  recent versions of MySQL, a foreign key constraint prevents
  deleting build lives. When attempting to delete a build life, an
  error similar to the following shows up on screen:
  PersistenceException: Error removing build life: ## object in
  database
  

Local fix

• Run the following two SQL statements against the UrbanCode Build
  MySQL database:
  
  ALTER TABLE WORKFLOW_CASE DROP FOREIGN KEY WC_BUILD_LIFE_FK;
  ALTER TABLE WORKFLOW_CASE ADD CONSTRAINT WC_BUILD_LIFE_FK
    FOREIGN KEY (BUILD_LIFE_ID)
    REFERENCES BUILD_LIFE (ID)
    ON DELETE CASCADE;
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All UrbanCode Build setups that use MySQL 5.7+               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Due to a change in the way "ON DELETE CASCADE" works in more *
  * recent versions of MySQL, a foreign key constraint in the    *
  * database prevents deleting build lives. When attempting to   *
  * delete a build life, an error similar to the following shows *
  * up on screen and the delete operation fails:                 *
  * com.urbancode.ubuild.domain.persistent.PersistenceException: *
  * Error removing build life: ## object in database             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to UrbanCode Build 6.1.2.3 or manually execute the   *
  * following SQL statements against the MySQL database:         *
  *                                                              *
  * ALTER TABLE WORKFLOW_CASE DROP FOREIGN KEY WC_BUILD_LIFE_FK; *
  * ALTER TABLE WORKFLOW_CASE ADD CONSTRAINT WC_BUILD_LIFE_FK    *
  *   FOREIGN KEY (BUILD_LIFE_ID)                                *
  *   REFERENCES BUILD_LIFE (ID)                                 *
  *   ON DELETE CASCADE;                                         *
  ****************************************************************
  

Problem conclusion

• Deleting a build life will cascade properly to relevant tables
  in MySQL database
  

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

  URBANCODE BUILD

• Fixed component ID

  5725P5700

Applicable component levels

• R610 PSN

     UP

• R610 PSY

     UP

• R611 PSN

     UP

• R611 PSY

     UP

• R612 PSN

     UP

• R612 PSY

     UP