MQSeries.net :: View topic

nmaddisetti · Posted: Thu Oct 22, 2009 6:21 am Post subject:

Hi All,

I installed WMB 6.1.0.2(tool kit and runtime) and installed fixpack 6.1.0.5 for runtime on Windows XP 64 bit OS.

I am not getting "MQSeries DataDirect Technologies 5.00 64-BIT Oracle" driver.

what is wrong I am not getting.

Broker is working but I am not able to connect to Oracle on the same box.
I installed 64 bit Connect for ODBC from DataDirect site it is giving error and here is the user trace:

Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version ; formatter version 6102

2009-10-21 23:55:47.967792 1836 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'Test_MsgFlow.MQInput'.
2009-10-21 23:55:47.968238 1836 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'Test_MsgFlow.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-10-21 23:55:47.968494 1836 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'Test_MsgFlow.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-10-21 23:55:47.968555 1836 UserTrace BIP6061I: Parser type ''BLOB'' created on behalf of node 'Test_MsgFlow.MQInput' to handle portion of incoming message of length '4' bytes beginning at offset '364'. Parser type selected based on value ''NONE'' from previous parser.
2009-10-21 23:55:56.128395 1836 Error BIP2628E: Exception condition detected on input node 'Test_MsgFlow.MQInput'.
The input node 'Test_MsgFlow.MQInput' 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.
2009-10-21 23:55:56.128456 1836 RecoverableException BIP2230E: Error detected whilst processing a message in node 'Test_MsgFlow.Compute'.
The message broker detected an error whilst processing a message in node 'Test_MsgFlow.Compute'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2009-10-21 23:55:56.128486 1836 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.
2009-10-21 23:55:56.128505 1836 DatabaseException BIP2322E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''.
The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''
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.
2009-10-21 23:55:57.128952 1836 Error BIP2648E: Message backed out to a queue; node 'Test_MsgFlow.MQInput'.
Node 'Test_MsgFlow.MQInput' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2009-10-21 23:55:57.129905 1836 UserTrace BIP2638I: The MQ output node 'Test_MsgFlow.MQInput' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''. The MQCC was '0' and the MQRC was '0'.
2009-10-21 23:55:57.129936 1836 UserTrace BIP2615I: The WebSphere MQ input node 'Test_MsgFlow.MQInput' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
No user action required.

Threads encountered in this trace:
1836

Can some one throw some light where should I concentrate to resove the problem.

Thanks & Regards,
Venkat.