MQSeries.net :: View topic - how to catch an ODBC Error and process the message into a di

artham · Posted: Fri Apr 05, 2002 7:29 am Post subject:

for a message getting processed throgh a flow we use ODBC to talk to Oracle 8.1.6 I get an error saying

2002-04-05 12:25:07.436999 744 Error BIP2628E: Exception condition detected on input node 'X'.
The input node 'X' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.

Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2002-04-05 12:25:07.436999 744 DatabaseException BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
2002-04-05 12:25:07.436999 744 DatabaseException BIP2322E: Database error: SQL State 'HY000'; Native Error Code '3114'; Error Text '[Oracle][ODBC][Ora]ORA-03114: not connected to ORACLE
'.
The error has the following diagnostic information: SQL State 'HY000' SQL Native Error Code '3114' SQL Error Text '[Oracle][ODBC][Ora]ORA-03114: not connected to ORACLE
'
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
2002-04-05 12:25:07.639999 744 Error BIP2628E: Exception condition detected on input node 'X'.
The input node 'X' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2002-04-05 12:25:07.639999 744 DatabaseException BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
2002-04-05 12:25:07.639999 744 DatabaseException BIP2322E: Database error: SQL State 'HY000'; Native Error Code '3114'; Error Text '[Oracle][ODBC][Ora]ORA-03114: not connected to ORACLE
'.
The error has the following diagnostic information: SQL State 'HY000' SQL Native Error Code '3114' SQL Error Text '[Oracle][ODBC][Ora]ORA-03114: not connected to ORACLE

MY QUESTION IS:

how do I catch an error like this in the Compute NODE and process it through an error handling process to a different queue.