IBM Support

JR50444: DATAINTEGRITYVIOLATIONEXCEPTION OCCURS WHEN SERVER STARTS OR YOU USE BPMINSTALLOFFLINEPACKAGE

Subscribe

You can track all active APARs for this component.

 

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:
    ホ6/3/14 6:02:11:314 BSTレ     FFDC
    Exception:org.springframework.dao.
      DataIntegrityViolationException
    SourceId:com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport
    ProbeId:isTransactionFailure-NoRetryForException
    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'.
     at 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
      (JdbcTemplate.java:866)
     at com.lombardisoftware.server.ejb.persistence.dao.
      UserGroupDAO.deleteGroups(UserGroupDAO.java:374)
      (GroupCore.java:1488)
     at com.lombardisoftware.server.core.GroupCore$4.call
      (GroupCore.java:1484)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport.executeInExistingTransaction
      (ProgrammaticTransactionSupport.java:582)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport.execute
      (ProgrammaticTransactionSupport.java:296)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport.execute
      (ProgrammaticTransactionSupport.java:198)
     at com.lombardisoftware.server.core.GroupCore.deleteGroups
      (GroupCore.java:1484)
     at com.lombardisoftware.server.core.GroupCore$5.call
      (GroupCore.java:1534)
     at com.lombardisoftware.server.core.GroupCore$5.call
      (GroupCore.java:1515)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport$1.doInTransaction
      (ProgrammaticTransactionSupport.java:409)
    
    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 happens only if interim fix JR49928 or JR48877 is
    installed.
    

Local fix

Problem summary

  • The exception occurs when IBM BPM tries to delete orphaned
    groups when the server starts or when you use the
    BPMInstallOfflinePackage command and exposed items are based on
    or depend on those orphaned groups.
    

Problem conclusion

  • A fix is available that checks whether there are exposed items
    before deleting the groups, preventing you from deleting those
    groups.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR50444:
    
    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 JR50444, 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 number

    JR50444

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-06

  • Closed date

    2014-08-07

  • Last modified date

    2014-08-07

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 August 2014