| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Tuning Odbc connection |
« View previous topic :: View next topic » |
| Author |
Message
|
| KoGor |
 Posted: Tue Sep 12, 2017 2:35 pm Post subject: Tuning Odbc connection |
 |
|
Voyager
Joined: 09 Nov 2005
Posts: 81
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 |
|
 |
| mqjeff |
| Posted: Wed Sep 13, 2017 3:24 am Post subject: Re: Tuning Odbc connection |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| 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.
_________________
chmod -R ugo-wx / |
|
| 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
|
|
|
|
