| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| odbc connection setting in broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| lalli_urs |
 Posted: Mon Nov 04, 2013 1:04 pm Post subject: odbc connection setting in broker |
 |
|
Novice
Joined: 10 Nov 2010
Posts: 10
|
The below odbc connection setting are used by me.
[USERDB]
Driver=/usr/wmb6/DD64/lib/xxx20.so
Description=DataDirect 5.0 64bit Oracle Wire Protocol
HostName=Dev144
PortNumber=1522
ServiceName=CSBLIVE.lloydstsb.co.uk
CatalogOptions=0
AlternateServers=(HostName=Dev143:PortNumber=1522:ServiceName=Live)
LoadBalancing=1
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
1.In the above setting, there is HostName & alternate servers, Is the broker will only connect to the database server mentioned in the alternate server name incase the HostName server is not available?
2.If the first question answer is No, then 'is load will be shared equally on both the servers(Dev144 & Dev143)'.
3.We have experienced slowness in broker when the server mentioned in the hostname was down, is there any specific region? I believe if the hostname server name is down then immediately it should route to the alternate server name but it is taking long time to process each transaction.
Can you someone please clarify me the above questions. 
I am using Message broker version 6.0.
Thanks in advance for you support. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Nov 04, 2013 1:19 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Before anyone else says it, are you aware that V6 went out of support several years ago?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 04, 2013 1:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
| Before anyone else says it, are you aware that V6 went out of support several years ago? |
| lalli_urs wrote: |
| ServiceName=CSBLIVE.lloydstsb.co.uk |
Says it all.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 04, 2013 1:32 pm Post subject: Re: odbc connection setting in broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lalli_urs wrote: |
| 1.In the above setting, there is HostName & alternate servers, Is the broker will only connect to the database server mentioned in the alternate server name incase the HostName server is not available? |
Yes
| lalli_urs wrote: |
| 2.If the first question answer is No, then 'is load will be shared equally on both the servers(Dev144 & Dev143)'. |
It's not No
| lalli_urs wrote: |
| 3.We have experienced slowness in broker when the server mentioned in the hostname was down, is there any specific region? |
Yes
| lalli_urs wrote: |
| I believe if the hostname server name is down then immediately it should route to the alternate server name but it is taking long time to process each transaction. |
Well if it wasn't routing to the alternate server but was still using the primary (which is down) it wouldn't be working at all would it?
So it tries a DB operation against the downed primary. This of course times out. So it tries the alternate, which works. Next time it tries a DB operation it tries the downed primary, which is still down and the operation times out. So it tries the alternate. Hence you get latency to the alternate equivalent to the time out interval of the ODBC call to the primary.
| lalli_urs wrote: |
| Can you someone please clarify me the above questions. |
Hope that helps.
| lalli_urs wrote: |
| I am using Message broker version 6.0. |
Get a newer version of WMB. And some HA software for your primary DB server.
| lalli_urs wrote: |
| Thanks in advance for you support. |
You're beyond support. In every sense. I mentioned this to you over a year ago. Things will only get worse. Even the management of that challenged institution should realise this.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Nov 06, 2013 5:34 am Post subject: Re: odbc connection setting in broker |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| lalli_urs wrote: |
| 3.We have experienced slowness in broker when the server mentioned in the hostname was down, is there any specific region? I believe if the hostname server name is down then immediately it should route to the alternate server name but it is taking long time to process each transaction. |
I guess this slowness depends on TCP timeout setting. Please check this value at OS level, because its default value is relatively high in the most OS, e.g. 2*45 seconds. |
|
| 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
|
|
|
|
