JR51659: BPD INSTANCES FAIL WITH ORA-02049 ERRORS

8.5.5.0-WS-BPM-IFJR51659
8.5.0.1-WS-BPM-IFJR51659
8.0.1.3-WS-BPM-IFJR51659
8.0.1.1-WS-BPM-IFJR51659
8.0.1.2-WS-BPM-IFJR51659
7.5.1.2-WS-BPM-IFJR51659
7.5.1.1-WS-BPM-IFJR51659
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

• If you use an Oracle database, you might occasionally see
  exceptions like the following exception in the SystemOut.log
  file:
  ﾎ10/28/14 4:04:19:662 CDTﾚ 0000008e wle_scheduler E
  CWLLG0181E: An exception occurred during execution of task 108.
  Error: PreparedStatementCallback; bad SQL grammar ﾎSELECT
  BPD_INSTANCE_ID FROM LSW_BPD_INSTANCE WHERE BPD_INSTANCE_ID = ?
  FOR UPDATEﾚ; nested exception is
  java.sql.SQLSyntaxErrorException: ORA-02049: timeout:
  distributed transaction waiting for lock
  com.lombardisoftware.core.TeamWorksException:
  PreparedStatementCallback; bad SQL grammar ﾎSELECT
  BPD_INSTANCE_ID FROM LSW_BPD_INSTANCE WHERE BPD_INSTANCE_ID = ?
  FOR UPDATEﾚ; nested exception is
  java.sql.SQLSyntaxErrorException: ORA-02049: timeout:
  distributed transaction waiting for lock
   at com.lombardisoftware.core.TeamWorksException.
    asTeamWorksException(TeamWorksException.java:136)
   at com.lombardisoftware.bpd.runtime.engine.quartz.
    AbstractBpdTask.execute(AbstractBpdTask.java:130)
   at com.lombardisoftware.bpd.runtime.engine.quartz.
    AbstractBpdTask.execute(AbstractBpdTask.java:59)
   at com.lombardisoftware.server.scheduler.Engine.execute
    (Engine.java:796)
   at com.lombardisoftware.server.scheduler.Engine.access$300
    (Engine.java:78)
   at com.lombardisoftware.server.scheduler.Engine$1.run
    (Engine.java:503)
  
  And you might see failed business process definition (BPD)
  instances with the instanceError:
  
   "PreparedStatementCallback; bad SQL grammar ﾎSELECT
  BPD_INSTANCE_ID FROM LSW_BPD_INSTANCE WHERE BPD_INSTANCE_ID = ?
  FOR UPDATEﾚ; nested exception is
  java.sql.SQLSyntaxErrorException: ORA-02049: timeout:
  distributed transaction waiting for lock "
  

Local fix

Problem summary

• IBM BPM acquires an exclusive lock on a BPD instance for
  navigation to ensure that only one thread performs navigation
  steps at any time. If one thread requests an exclusive lock for
  an instance while another thread holds the lock and the other
  thread needs longer than the lock timeout for its navigation, a
  lock timeout might occur in the requesting thread. There are
  many reasons why a thread might need longer for navigation than
  the lock timeout that is configured for your database.
  

Problem conclusion

• A fix is/will be available that ensures ORA-02049 exceptions
  are synchronously retried similar to retries that happen for
  DB/2 deadlocks and lock timeouts.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR51659
  
  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 JR51659, 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 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