ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can we have more than one BAggregate table

Post new topic  Reply to topic
 Can we have more than one BAggregate table « View previous topic :: View next topic » 
Author Message
muralihegde
PostPosted: Sat Oct 09, 2004 5:55 am    Post subject: Can we have more than one BAggregate table Reply with quote

Centurion

Joined: 30 Apr 2002
Posts: 108

Hi,
We have WMQI 2.1 broker. We use the aggregation nodes extensively in our message flows. Under heavy load sometime this causes database dead locks and often time out from the BAggregate table.
One of reasons is that there is a sinlge table BAGGREGATE that the broker uses for aggregation nodes. This causes heavy transactions to a single physical table. It would be good if we could configure the different aggregation nodes to use different tables.

Maybe one set of messsage flows or execution group to use a table BAGG1 and others to use BAGG1 etc..
Or the Aggregation Nodes itself could take up a parameter for the table name. Of cource the table structure for all these additional should be same as the original BAGGREGATE table itself.
Is it possible to do this kind of configuration? Has anybody tired it? I know the default installation/configuraiton does not allow this.

By any tweaking/work around is it possible to achive the above?
-Thanks ...
Murali
Back to top
View user's profile Send private message Yahoo Messenger
siliconfish
PostPosted: Sat Oct 09, 2004 10:33 am    Post subject: Reply with quote

Master

Joined: 12 Aug 2002
Posts: 203
Location: USA

Database deadlocks with DB2
The three Aggregation nodes all use the broker database. If you are using DB2 as
this database, you may experience database deadlocks under stress conditions
when running with multiple threads. This will be identified by the WMQI event
log message 2322, with SQL State 40001. This is caused by a DB2 feature called
"next key locking".
If this problem occurs, then next key locking can be disabled by typing db2set
DB2_RR_TO_RS=YES in a DB2 command window and restarting the DB2 database
manager.
_________________
siliconfish
Back to top
View user's profile Send private message
kirani
PostPosted: Sat Oct 09, 2004 11:42 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

You can also think of using multiple broker configuration. Each broker will use different broker db.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can we have more than one BAggregate table
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.