JR50742: BPMINSTALLOFFLINEPACKAGE OR SERVER STARTS RESULTS IN DATAINTEGRITYVIOLATIONEXCEPTION

8.5.0.0-WS-BPM-IFJR50742
8.5.5.0-WS-BPM-IFJR50742
Download Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 6 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When the server starts or when you use the
  BPMInstallOfflinePackage administrative command, you might see
  the following DATAINTEGRITYVIOLATIONEXCEPTION:
  
  org.springframework.dao.DataIntegrityViolationException:
  PreparedStatementCallback; SQL ﾎDELETE FROM LSW_USR_GRP_XREF
  WHERE GROUP_ID = ?ﾚ; The DELETE statement conflicted with the
  REFERENCE constraint "LSWC_FAV_GRP_FK". The conflict occurred in
  database "BPMDB", table "dbo.LSW_FAVORITE", column 'GROUP_ID'.;
  nested exception is java.sql.BatchUpdateException: The DELETE
  statement conflicted with the REFERENCE constraint
  "LSWC_FAV_GRP_FK". The conflict occurred in database "BPMDB",
  table "dbo.LSW_FAVORITE", column 'GROUP_ID'.
  org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.
  translate(SQLStateSQLExceptionTranslator.java:114)
  at org.springframework.jdbc.support.
    SQLErrorCodeSQLExceptionTranslator.translate
    (SQLErrorCodeSQLExceptionTranslator.java:322)
  at org.springframework.jdbc.core.JdbcTemplate.execute
    (JdbcTemplate. java:607)
  at org.springframework.jdbc.core.JdbcTemplate.execute
    (JdbcTemplate.java:619)
  at org.springframework.jdbc.core.JdbcTemplate.batchUpdate
    (JdbcTempl...
  
  This exception occurs when IBM Business Process Manager (BPM)
  tries to delete orphaned groups that a favorite from another
  snapshot still points to.
  
  This issue occurs only if interim fix JR49928 or JR48877 is
  installed.
  

Local fix

Problem summary

• If either the BPMSnapshotCleanup or BPMDeleteSnapshot command
  ran before the other APARs that are related to snapshot deletion
  are applied, participant groups (called ?team? in V8.5 and
  later) might remain in the database. These orphaned participant
  groups or teams cause a data-integrity violation exception when
  the server starts or while an offline deployment package is
  being installed.
  

Problem conclusion

• A fix is/will be available that improves the repair function by
  clearing orphaned participant groups or teams automatically
  when the server starts.
  
  This fix is related to orphaned participant groups or teams
  whereas JR50444 covers the scenario of orphaned dynamic groups.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR50742:
  
  1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
  
  2. Select APAR or SPR, enter JR50742, and click Continue.
  
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  
  In addition to this interim fix, install the other interim fixes
  that are required for the BPMDeleteSnapshot and
  BPMSnapshotCleanup commands, which are listed in "Issues with
  BPMDeleteSnapshot and BPMSnapshotCleanup commands in IBM
  Business Process Manager (BPM)"
  (http://www.ibm.com/support/docview.wss?uid=swg21669992).
  

Temporary fix

• Not applicable
  

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

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R751 PSY

     UP

• R801 PSY

     UP

• R850 PSY

     UP

• R855 PSY

     UP