MQSeries.net :: View topic - Database error during Aggregation Nodes in WBIMB

funknor

I am currently trying to use aggregation nodes. I detect the following error during responses at aggregation nodes:
[IBM][CLI Driver][DB2/NT] SQL0803N One or more values in the INSERT statement, UPDATE ... and BAGGREGATE contains rows with empty fields. Any ideas?

When the reply messages are coming back, the aggregation reply node throws a database exception with the second received response. See below the error log.

I noticed that with the aggregation request node entries are created into the BAGGREGATE database, but the columns are empty (basically empty records, except an entry â€˜Nâ€™ in â€œunsolicitedâ€)

The aggregate reply node creates empty entries in the same table with â€˜Yâ€™ in â€œunsolicitedâ€. Can you help me with how to set up the aggregation nodes?

Here are the log entries:

Log 1:-------------------------

( WBRK_BROKER.default ) 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 the primary key, unique constraint or unique index identified by "1" constrains table "FUNKEN.BAGGREGATE" from having duplicate rows for those columns. 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 the primary key, unique constraint or unique index identified by "1" constrains table "FUNKEN.BAGGREGATE" from having duplicate rows for those columns. SQLSTATE=23505

'

Log 2:-------------------------

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.

( WBRK_BROKER.default ) 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.

Log 3:-------------------------

( WBRK_BROKER.default ) Database statement 'INSERT INTO FUNKEN.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 FUNKEN.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.

Log 4:-------------------------

( WBRK_BROKER.default ) Exception condition detected on input node 'EBS_Controller_OUT.Benefit'.

The input node 'EBS_Controller_OUT.Benefit' 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.

Log 5:-------------------------

( WBRK_BROKER.default ) Message broker internal error: diagnostic information 'Could not locate unknown message in broker database', 'MQ', '414d51205742524b5f514d2020202020a120823f20004902'.

An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.

Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.

Log 5:-------------------------

( WBRK_BROKER.default ) Exception condition detected on input node 'EBS_Controller_OUT.AggregateReply'.

The input node 'EBS_Controller_OUT.AggregateReply' detected an error whilst processing a message. The default message recovery processing of the node will have been invoked. The message being processed may have been reinstated on the input device or external software resource which provides the input data. This will be dependant on the capabilities of such devices or resources and, in the case of plug-in input nodes, on the features of the node itself. Other messages may be associated with this message which further describe the error condition.

Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.