IBM Support

JR52665: WITH INTERIM FIX JR49509 APPLIED, PROCESSINDEXFULLREINDEX COMMAND FAILS ON ORACLE (DUPLICATEKEYEXCEPTION)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With interim fix JR49509 applied, when you run the
    ProcessIndexFullReIndex command with Oracle as the database for
    IBM Business Process Manager (BPM), the following exception is
    written to the SystemOut.log file:
    
    
    BPMServerAdmi I BPMSearchIndexUpdateInstance failed due to: null
    java.lang.NullPointerException
    at
    com.ibm.bpm.server.commands.impl.internal.BPMSearchIndexUpdateIn
    stance.execute(BPMSearchIndexUpdateInstance.java:55)
    at
    com.ibm.ws.management.cmdframework.impl.RemoteCommandMgrImpl.adm
    inCmdExecute(RemoteCommandMgrImpl.java:335)
    at
    com.ibm.ws.management.cmdframework.impl.RemoteCommandMgrImpl.exe
    cute(RemoteCommandMgrImpl.java:292)
    ...
    
    As a result, the command does not re-index process instances and
    tasks to the Process Portal index.
    
    
    PRODUCTS AFFECTED
    IBM BPM Advanced
    IBM BPM Standard
    IBM BPM Express
    

Local fix

Problem summary

  • Logic in the processIndexFullReIndex command sets the value of
    the column INDEX_START_TIME in the BPM_TASK_INDEX_JOB database
    table for a new row representing the full re-indexing job to the
    value of the most recent index job's INDEX_START_TIME value
    plus one millisecond. On Oracle, however, timestamp columns do
    not have millisecond granularity, just second granularity. As a
    result, Oracle views the INDEX_START_TIME as being equal for the
    existing and newly inserted rows and, because, this column is
    part of the primary key for the table, the DuplicateKeyException
    is thrown and the re-indexing job fails.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.0.1 that changes the logic
    to add one second to the last index job's INDEX_START_TIME value
    for the row to be inserted for the re-indexing job, resolving
    the issue.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52665:
    
     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 JR52665, 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.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR52665

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-25

  • Closed date

    2015-05-13

  • Last modified date

    2015-05-13

  • 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

  • R850 PSY

       UP

  • R856 PSY

       UP

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

Document Information

Modified date:
13 May 2015