| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Accesing 2 datasources in one message flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| santy |
 Posted: Fri Aug 13, 2010 1:40 am Post subject: Accesing 2 datasources in one message flow |
 |
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
Hi,
Message flow created in WMB 6.1, is accessing 2 databases (diff. data sources A and B) using CALL statement. It first access A datasource and then B source.
After running this message flow, we have encountered a problem of slowness of A database which has caused B database also to go down.
(we still don't know the root cause of the issue).
But we are thinking that, the problem could have been occoured because of this design.
I would like, is this possible? and also what precautions do we need to take for such design? and is it a standard practise for such designs? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Aug 13, 2010 4:11 am Post subject: Re: Accesing 2 datasources in one message flow |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santy wrote: |
| I would like, is this possible? and also what precautions do we need to take for such design? and is it a standard practise for such designs? |
It's possible, subject to the rules about mixing providers which I don't think applies here.
The precautions you need to take are the same as you'd take for any application that uses databases; controling locking, select with index not tablescan, that sort of thing.
Your problem here is this:
| santy wrote: |
| we still don't know the root cause of the issue |
Just pointing at WMB and going "well it could be that" is unproductive and unhelpful. It could equally have been a DBA running a reorg (and from the information you've provided sounds more likely).
How slow was database A? How was this measured? What work was in progress? What queries were running? What was the status of the server on which it was running?
How do you know the crash of database B was connected to the slowness of A? What error codes did it log? What work was in progress? What queries were running?
When was the WMB flow last updated? When were the databases last maintained? Are they maintained regularly & automatically? How often is runstats done?
Don't just point at WMB. Work the problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
