IZ40853: ODBC STATEMENT IS UNUSABLE AFTER ORA-01003 FAILURE

WebSphere Message Broker V6.1 - Fix Pack 6.1.0.7

APAR status

• Closed as program error.

Error description

• When an Oracle table is dropped and recreated message flow
  generates ORA-01003 errors.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Message Broker V6.0   *
  *                 and V6.1 using an Oracle user database.      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A message flow is not able to access    *
  *                      an Oracle database table after that     *
  *                      table has been dropped and recreated    *
  *                      between transactions.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If an Oracle database table that is used by a message flow is
  dropped, the next transaction correctly fails with "ORA-00942:
  table or view does not exist". Subsequent transactions fail
  with the message "ORA-01003: no statement parsed". Even when
  the table is recreated, transactions continue to fail with
  ORA-01003 because Oracle has invalidated the ODBC statement.
  

Problem conclusion

• When the message flow receives the Oracle database error
  ORA-01003, it releases the ODBC database connection and all
  the ODBC statements associated with it. A new connection will
  be requested for the next transaction.
  

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

  WMB SOL SPARC

• Fixed component ID

  5724J0502

Applicable component levels

• R100 PSY

     UP