| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2371 error on Aggregate Reply |
« View previous topic :: View next topic » |
| Author |
Message
|
| guest |
 Posted: Wed Nov 19, 2003 10:46 am Post subject: 2371 error on Aggregate Reply |
 |
|
Acolyte
Joined: 11 Aug 2003
Posts: 52
|
Can someone tell me how the Aggregate information is stored? Is it somehow linked with the Aggregate Name? Whenever my fan-in portion of an Aggregate Request comes into the Aggregate Reply node, I get a 2371, which is a database error saying that the database statement &1 could not be executed. I'm think that maybe I need to create a DB2 table to correspond with the Agg name in the node. Any points in the right direction would be a big help.
Thanks
Paul Siracusa |
|
| Back to top |
|
 |
| TonyD |
| Posted: Wed Nov 19, 2003 1:51 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| Aggregate fan-out, fan-in processing includes the temporary storage of information in the broker table BAGGREGATE.....you do not have to create any tables associated with aggregate processing. Does the Event Log or db2diag provide more inormation about the database error? |
|
| Back to top |
|
|
| guest |
| Posted: Thu Nov 20, 2003 7:08 am Post subject: |
|
|
Acolyte
Joined: 11 Aug 2003
Posts: 52
|
| Yes, there is thanks. It looks like there is a primary key violation saying that the information is not unique. Whenever I look at the trace, the reply information, and unknown (which are the primary key columns) is nulled out. Is this supposed to be supplied from the MQReply node? |
|
| Back to top |
|
|
| TonyD |
| Posted: Thu Nov 20, 2003 3:13 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| The primary key of the BAGGREGATE table includes the MQMD MsgId of the fan-out messages. This is used to resolve whether the fan-in replies, which must contain this in their CorrelId, are valid and have all arrived. Is it possible that you have a fixed MsgId in one or more of your fan-out messages, and that there have been uncompleted fan-out/ fan-in executions? If you are working in a 'sandpit' environment you could delete the rows in BAGGREGATE and then try your flow. However you should take steps to make the MsgIds unique or you will encounter problems if you have more than one instance of the fan-out flow running concurrently. |
|
| Back to top |
|
|
| guest |
| Posted: Fri Nov 21, 2003 11:56 am Post subject: |
|
|
Acolyte
Joined: 11 Aug 2003
Posts: 52
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
