JR42340: INSERTION OF DUPLICATE TIMING INTERVAL INTO PDW DATABASE, CAUSING TRACKING GROUP CREATION TO FAIL

Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When creating a tracking group from a process application, there
  are cases where a timing interval defined in the process
  application may exist in the Performance Data Warehouse (PDW)
  database (from a previously created tracking group from a
  different process applications, or, within a single process
  application, multiple versions of an imported toolkit
  (containing an auto-generated timing interval) may be
  associated, resulting in "multiple definitions" of the same
  timing interval within the application).  In these cases, when
  the new tracking group is created, there is an attempt to create
  a timing interval that already exists in the PDW database,
  resulting in an exception similar to the following in
  SystemOut.log (example illustrates the error on an Oracle
  database):
  
  org.springframework.dao.DataIntegrityViolationException:
  PreparedStatementCallback; SQL [insert into LSW_TIMING_INTERVAL
  (TIMING_INTERVAL_ID,EXTERNAL_UNIQUE_ID,NAME,DESCRIPTION,START_BO
  UND,ENDBOUND,ARCHIVED,VERSION,LAST_MODIFIED,SYSTEM_ID,LAST_MODIF
  IED_BYUSERID,IS_AUTO) values (?,?,?,?,?,?,?,?,?,?,?,?)];
  ORA-00001: unique constraint (PDWUSR.LSWC_TMNGNTRVL_UQ1)
  violated
  
  As a result the tracking group creation fails.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM Express, BPM Standard and BPM  *
  *                  Advanced.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Creation of a tracking group may        *
  *                      attempt to insert a timing interval     *
  *                      which already exists, causing the       *
  *                      creation to fail.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When creating a tracking group from a process application,
  there
  are cases where a timing interval defined in the process
  application may exist in the Performance Data Warehouse (PDW)
  database (from a previously created tracking group from a
  different process applications, or, within a single process
  application, multiple versions of an imported toolkit
  (containing an auto-generated timing interval) may be
  associated, resulting in "multiple definitions" of the same
  timing interval within the application).  In these cases, when
  the new tracking group is created, there is an attempt to
  create
  a timing interval that already exists in the PDW database,
  resulting in an exception similar to the following in
  SystemOut.log (example illustrates the error on an Oracle
  database):
  org.springframework.dao.DataIntegrityViolationException:
  PreparedStatementCallback; SQL [insert into LSW_TIMING_INTERVAL
  (TIMING_INTERVAL_ID,EXTERNAL_UNIQUE_ID,NAME,DESCRIPTION,START_BO
  UND,ENDBOUND,ARCHIVED,VERSION,LAST_MODIFIED,SYSTEM_ID,LAST_MODIF
  IED_BYUSERID,IS_AUTO) values (?,?,?,?,?,?,?,?,?,?,?,?)];
  ORA-00001: unique constraint (PDWUSR.LSWC_TMNGNTRVL_UQ1)
  violated
  As a result the tracking group creation fails.
  

Problem conclusion

• The PDW logic was improved to recognize that a second timing
  interval (with the same ID) could arrive; the second interval
  will be treated as an update instead of an insertion.
  
  An interim fix for BPM V7.5.1 is available in Fix Central.
  Download and install the interim fix using Installation Manager
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP