MQSeries.net :: View topic

Meow · Posted: Thu Jan 29, 2004 2:20 am Post subject:

I am trying to work on aggregate nodes. i am getting the following error when i am putting the message flow

Below are the Trace file details:

2004-01-28 18:31:31.077999 552 UserTrace BIP2638I: The MQ output node 'Test_Aggregate.Replies.MQOutput1' attempted to write a message to the specified queue 'TEST.AGGREGATE.RESPONSE' connected to queue manager 'MYQMGR'. The MQCC was 0 and the MQRC was 0.
2004-01-28 18:31:31.077999 552 UserTrace BIP2622I: Message successfully output by MQ output node 'Test_Aggregate.Replies.MQOutput1' to queue 'TEST.AGGREGATE.RESPONSE' on queue manager 'MYQMGR'.
2004-01-28 18:31:31.077999 552 UserTrace BIP4412I: Corresponding request record not found for the reply message.
An AggregateReply node has received a message at its 'in' terminal. No corresponding record of a request message being sent could be found in the database. See subsequent messages to determine how this situation has been handled.
It is possible that extraneous messages are arriving at the AggregateReply node 'in' terminal. Check your flow to ensure that the only messages arriving here are replies to request messages previously sent out and passed through an AggregateRequest node. It is possible that this message is a valid reply but part of an aggregation which previously timed out. It is possible that this is a reply to a message which has not yet been recorded by an AggregateRequest node. This can happen if request messages are sent outside of transactional control. Adjust your transaction settings to ensure that messages are sent under transactional control.
2004-01-28 18:31:31.077999 552 UserTrace BIP4413I: Storing unknown message persistently for subsequent processing.
The message has been stored persistently by the AggregateReply node. If it is subsequently discovered to be a valid reply in an aggregation then it will be processed as such at that time. If a number of seconds passes as specified by the 'unknown timeout' attribute, then the message will be propagated to the 'unknown' terminal.
No user action required.
2004-01-28 18:31:31.077999 552 UserTrace BIP2231E: Error detected whilst processing a message 'Test_Aggregate.MQInput1'.
The message broker detected an error whilst processing a message in node 'Test_Aggregate.MQInput1'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2004-01-28 18:31:31.077999 552 RecoverableException BIP2230E: Error detected whilst processing a message in node 'Test_Aggregate.PASSENGER Response'.
The message broker detected an error whilst processing a message in node 'Test_Aggregate.PASSENGER Response'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2004-01-28 18:31:31.077999 552 RecoverableException BIP2230E: Error detected whilst processing a message in node 'Test_Aggregate.Replies.MQOutput1'.
The message broker detected an error whilst processing a message in node 'Test_Aggregate.Replies.MQOutput1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2004-01-28 18:31:31.077999 552 DatabaseException BIP2371E: Database statement 'INSERT INTO DB2ADMIN.BAGGREGATE (BrokerUUID , aggregateName , replyId , replyProtocol , timeout , data , unsolicited , messageDomain , messageFormat , messageSet , messageType , encoding , ccsid) VALUES ( ? , ? , ? , ? , ? , ? , 'Y' , ? , ? , ? , ? , ? , ? )' could not be executed.
A message flow node attempted to execute a database statement. However, the database returned an error when executing the statement 'INSERT INTO DB2ADMIN.BAGGREGATE (BrokerUUID , aggregateName , replyId , replyProtocol , timeout , data , unsolicited , messageDomain , messageFormat , messageSet , messageType , encoding , ccsid) VALUES ( ? , ? , ? , ? , ? , ? , 'Y' , ? , ? , ? , ? , ? , ? )'.
If necessary, correct the message flow and redeploy the message broker.
2004-01-28 18:31:31.077999 552 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.
2004-01-28 18:31:31.077999 552 DatabaseException BIP2322E: Database error: SQL State '23505'; Native Error Code '-803'; Error Text '[IBM][CLI Driver][DB2/NT] SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because they would produce duplicate rows for a table with a primary key, unique constraint, or unique index. SQLSTATE=23505
'.
The error has the following diagnostic information: SQL State '23505' SQL Native Error Code '-803' SQL Error Text '[IBM][CLI Driver][DB2/NT] SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because they would produce duplicate rows for a table with a primary key, unique constraint, or unique index. SQLSTATE=23505
'
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.
2004-01-28 18:31:31.077999 552

can some one guide me what could be the problem?