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 IndexWebSphere Message Broker SupportTuning Odbc connection

Post new topicReply to topic
Tuning Odbc connection View previous topic :: View next topic
Author Message
KoGor
PostPosted: Tue Sep 12, 2017 2:35 pm Post subject: Tuning Odbc connection Reply with quote

Voyager

Joined: 09 Nov 2005
Posts: 78
Location: Moscow,Russia.

Hi all!
I have WMB 7.0.0.8 on AIX installed. I wrote simple flow that make a select from DB2 9.7 into message flow memory (simple cache). There is a simple two fields table with queue manager name and queue name for dynamic routing. It worked well till today while I increased number of records in DB2 table from 27000 till 48000 and suddenly the flow had stopped working. I tried to debug the message flow and found out that if there were about 30K records in table it worked, if I try to load to broker more than 30K records it just hung for some indefinite timeout. However there is no problem with the DB2, I can select all rows in a moment.
I have tried to increase execution group Java heap size till 512MB but no luck. May be there is some buffer in ODBC driver that just is not big enough for sql result?
Thank you for ideas!
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Sep 13, 2017 3:24 am Post subject: Re: Tuning Odbc connection Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17386

KoGor wrote:
Hi all!
I have WMB 7.0.0.8 on AIX installed. I wrote simple flow that make a select from DB2 9.7 into message flow memory (simple cache). There is a simple two fields table with queue manager name and queue name for dynamic routing. It worked well till today while I increased number of records in DB2 table from 27000 till 48000 and suddenly the flow had stopped working. I tried to debug the message flow and found out that if there were about 30K records in table it worked, if I try to load to broker more than 30K records it just hung for some indefinite timeout. However there is no problem with the DB2, I can select all rows in a moment.
I have tried to increase execution group Java heap size till 512MB but no luck. May be there is some buffer in ODBC driver that just is not big enough for sql result?
Thank you for ideas!


If you switch to a supported version, you will likely find a lot more options in this area.

If your employer/customer won't switch to a supported version, explain the contrast between ROI and accumulated risk - the older the version of software you are using, the more risk has accumulated - particularly in the areas of security.
_________________
Read, Think, Try, Repeat
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportTuning Odbc connection
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.