RE: windows odbc connection to connection mana....
Justin couldn't connect a Windows ODBC DSN to an sqlhosts group of three Connection Manager SLAs, getting "Server sla_cm_grp is not listed as a dbserver name in sqlhosts", though individual CMs worked and the group worked from dbaccess on Linux. Art Kagel pointed to an IBM technote: since Windows has no sqlhosts file, the group definition must be added manually to the registry, which fixed it. A follow-up question - whether the c=1 random/load-distribution option works in CSDK 3.50.TC5, since connections always went to the same CM - got no definite answer; Art suggested asking IBM and Paul Watson noted CM itself doesn't round-robin. No resolution recorded for that part.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Does the c=1 option work for the windows CSDK 3.50.TC5? I have the option
listed in the group registry key, but always seems to go back to the same
server (the first one alphabetically).
-Justin
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art Kagel
Sent: Thursday, June 06, 2013 4:50 PM
To: ids@iiug.org
Subject: Re: windows odbc connection to connection mana.... [30450]
You are almost right, c=1 means that instead of every client connecting in
the specified order starting with the first listed connection name each
client selects one of the connection names at random then cycles through
the list if the first one it tries doesn't respond. Not exactly round
robin, but it does do some load distribution if not balancing.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
jkillen@allamericanasphalt.com> wrote:
> Art,
>
> Thanks - that works great! I think when we deploy the connection setup to
> the
> client machines we'll be using registry files anyway, so requiring a few
> extra
> keys is no big deal.
>
> As for the round-robin, I was under the impression that the option "c=1"
> setup
> servers for round-robin distribution, but perhaps I'm mistaken. Round-robin
> connections to the CM's isn't a requirement for us, so it's not something
> I'm
> going to worry about.
>
> -Justin
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Thursday, June 06, 2013 2:50 PM
> To: ids@iiug.org
> Subject: Re: windows odbc connection to connection mana.... [30448]
>
> Justin:
>
> See this link for how to configure windows apps to use sqlhsots "groups":
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21447622
>
> You have to manually edit the registry to enter the definition of the group
> since there is no sqlhosts file on the windows side.
>
> Also, AFAIK, using groups does not round robin through the group members,
> it just sequentially tries each group member, in the order they are listed,
> until one of them responds. Groups are for failover not load balancing
> (hence the need for Connection Manager). You can make it kind of
> round-robin/load-balancing by using the environment variables
> INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client
> will wait for a response from SOME group member before returning an error
> and how many retries the client will make within that time. Indirectly
> that will configure the time the client waits for each member before trying
> to connect to the next member of the group.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> other organization with which I am associated either explicitly,
> implicitly, or by inference. Neither do those opinions reflect those of
> other individuals affiliated with any entity with which I am affiliated nor
> those of the entities themselves.
>
> On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
> jkillen@allamericanasphalt.com> wrote:
>
> > I have 3 connection manager (Linux) instances whose SLA's are in a group
> in
> > sqlhosts (group option c=1). When I run dbaccess on any of those
> machines,
> > the
> > SLA group is listed as an option, and I can connect to the group (it will
> > round-robin my connection to one of the connection managers).
> > Now that it is working on the servers themselves, I'd like to get it to
> > work
> > on my windows PC. I've added the SLA for each server as well as the SLA
> > group
> > into the system via Setnet32. When creating an ODBC connection, I'm using
> > the
> > following information:
> >
> > Server Name: sla_cm_grp
> > Host Name: -
> > Service: -
> > Protocol: group
> > Options: c=1
> >
> > When I try to test the connection, I get the error:
> > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not
> listed
> > as
> > a dbserver name in sqlhosts"
> > If I use any of the connection managers directly I can connect just
> fine, I
> > just can't get it to connect to the group. Is this option supported by
> the
> > ODBC framework?
> >
> > I'm using CSDK version 3.50 TC8 on the windows machine. Server is running
> > on
> > Linux, Informix 12.1
> >
> > -Justin
> >
> >
> >
> >
>
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --089e013d1a4a91d12904de834cd0
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--089e01493c1ea0be0604de84f9f1
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Hmm, don't know. One thing to note: Groups will never failover to a
secondary that is read-only (just found this one out yesterday). This was
a change to the behavior of groups somewhere around v11.10 of the server
(so v3.10 of the CSDK). So, could that be the problem you are seeing?
Also, I don't remember when the c=1 option was first available (don't
think that it goes all the way back) so the CSDK/iConnect on your Windows
boxes may not support this if they are older. IBM can research that one
for you if your version on windows isn't up to snuff. Looking back I see
you said you are using v3.50.TC8 and that SHOULD be good, but again, not
sure.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Thu, Aug 8, 2013 at 1:10 PM, Justin Killen <
jkillen@allamericanasphalt.com> wrote:
> Does the c=1 option work for the windows CSDK 3.50.TC5? I have the option
> listed in the group registry key, but always seems to go back to the same
> server (the first one alphabetically).
>
> -Justin
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Thursday, June 06, 2013 4:50 PM
> To: ids@iiug.org
> Subject: Re: windows odbc connection to connection mana.... [30450]
>
> You are almost right, c=1 means that instead of every client connecting in
> the specified order starting with the first listed connection name each
> client selects one of the connection names at random then cycles through
> the list if the first one it tries doesn't respond. Not exactly round
> robin, but it does do some load distribution if not balancing.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> other organization with which I am associated either explicitly,
> implicitly, or by inference. Neither do those opinions reflect those of
> other individuals affiliated with any entity with which I am affiliated nor
> those of the entities themselves.
>
> On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
> jkillen@allamericanasphalt.com> wrote:
>
> > Art,
> >
> > Thanks - that works great! I think when we deploy the connection setup to
> > the
> > client machines we'll be using registry files anyway, so requiring a few
> > extra
> > keys is no big deal.
> >
> > As for the round-robin, I was under the impression that the option "c=1"
> > setup
> > servers for round-robin distribution, but perhaps I'm mistaken.
> Round-robin
> > connections to the CM's isn't a requirement for us, so it's not something
> > I'm
> > going to worry about.
> >
> > -Justin
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Art
> > Kagel
> > Sent: Thursday, June 06, 2013 2:50 PM
> > To: ids@iiug.org
> > Subject: Re: windows odbc connection to connection mana.... [30448]
> >
> > Justin:
> >
> > See this link for how to configure windows apps to use sqlhsots "groups":
> >
> > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
> >
> > You have to manually edit the registry to enter the definition of the
> group
> > since there is no sqlhosts file on the windows side.
> >
> > Also, AFAIK, using groups does not round robin through the group members,
> > it just sequentially tries each group member, in the order they are
> listed,
> > until one of them responds. Groups are for failover not load balancing
> > (hence the need for Connection Manager). You can make it kind of
> > round-robin/load-balancing by using the environment variables
> > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client
> > will wait for a response from SOME group member before returning an error
> > and how many retries the client will make within that time. Indirectly
> > that will configure the time the client waits for each member before
> trying
> > to connect to the next member of the group.
> >
> > Art
> >
> > Art S. Kagel
> > Advanced DataTools (www.advancedatatools.com)
> > Blog: http://informix-myview.blogspot.com/
> >
> > Disclaimer: Please keep in mind that my own opinions are my own opinions
> > and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> > other organization with which I am associated either explicitly,
> > implicitly, or by inference. Neither do those opinions reflect those of
> > other individuals affiliated with any entity with which I am affiliated
> nor
> > those of the entities themselves.
> >
> > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
> > jkillen@allamericanasphalt.com> wrote:
> >
> > > I have 3 connection manager (Linux) instances whose SLA's are in a
> group
> > in
> > > sqlhosts (group option c=1). When I run dbaccess on any of those
> > machines,
> > > the
> > > SLA group is listed as an option, and I can connect to the group (it
> will
> > > round-robin my connection to one of the connection managers).
> > > Now that it is working on the servers themselves, I'd like to get it to
> > > work
> > > on my windows PC. I've added the SLA for each server as well as the SLA
> > > group
> > > into the system via Setnet32. When creating an ODBC connection, I'm
> using
> > > the
> > > following information:
> > >
> > > Server Name: sla_cm_grp
> > > Host Name: -
> > > Service: -
> > > Protocol: group
> > > Options: c=1
> > >
> > > When I try to test the connection, I get the error:
> > > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not
> > listed
> > > as
> > > a dbserver name in sqlhosts"
> > > If I use any of the connection managers directly I can connect just
> > fine, I
> > > just can't get it to connect to the group. Is this option supported by
> > the
> > > ODBC framework?
> > >
> > > I'm using CSDK version 3.50 TC8 on the windows machine. Server is
> running
> > > on
> > > Linux, Informix 12.1
> > >
> > > -Justin
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
*******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> > --089e013d1a4a91d12904de834cd0
> >
> >
> >
> >
>
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> >
>
>
Hello.
Supposing you have a group of servers, it should randomly connect to all of
them.
For more information, our friend Fernando Nunes has made a complete article
about sqlhosts features, check it out:
http://informix-technology.blogspot.com.br/2013/08/sqlhosts-options-opcoes-do-sq
lhosts.html
Regards.
Alexandre Marini
IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10
IBM Information Management Informix Technical Professional
IBM Infosphere DataStage Technical Professional
Informix Senior DBA - Orizon Brasil
BRIUG website administrator
Informix independent consultant
> To: ids@iiug.org
> From: jkillen@allamericanasphalt.com
> Subject: RE: windows odbc connection to connection mana.... [31089]
> Date: Thu, 8 Aug 2013 13:10:54 -0400
>
> Does the c=1 option work for the windows CSDK 3.50.TC5? I have the option
> listed in the group registry key, but always seems to go back to the same
> server (the first one alphabetically).
>
> -Justin
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Thursday, June 06, 2013 4:50 PM
> To: ids@iiug.org
> Subject: Re: windows odbc connection to connection mana.... [30450]
>
> You are almost right, c=1 means that instead of every client connecting in
> the specified order starting with the first listed connection name each
> client selects one of the connection names at random then cycles through
> the list if the first one it tries doesn't respond. Not exactly round
> robin, but it does do some load distribution if not balancing.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> other organization with which I am associated either explicitly,
> implicitly, or by inference. Neither do those opinions reflect those of
> other individuals affiliated with any entity with which I am affiliated nor
> those of the entities themselves.
>
> On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
> jkillen@allamericanasphalt.com> wrote:
>
> > Art,
> >
> > Thanks - that works great! I think when we deploy the connection setup to
> > the
> > client machines we'll be using registry files anyway, so requiring a few
> > extra
> > keys is no big deal.
> >
> > As for the round-robin, I was under the impression that the option "c=1"
> > setup
> > servers for round-robin distribution, but perhaps I'm mistaken. Round-robin
> > connections to the CM's isn't a requirement for us, so it's not something
> > I'm
> > going to worry about.
> >
> > -Justin
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> > Kagel
> > Sent: Thursday, June 06, 2013 2:50 PM
> > To: ids@iiug.org
> > Subject: Re: windows odbc connection to connection mana.... [30448]
> >
> > Justin:
> >
> > See this link for how to configure windows apps to use sqlhsots "groups":
> >
> > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
> >
> > You have to manually edit the registry to enter the definition of the group
> > since there is no sqlhosts file on the windows side.
> >
> > Also, AFAIK, using groups does not round robin through the group members,
> > it just sequentially tries each group member, in the order they are listed,
> > until one of them responds. Groups are for failover not load balancing
> > (hence the need for Connection Manager). You can make it kind of
> > round-robin/load-balancing by using the environment variables
> > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client
> > will wait for a response from SOME group member before returning an error
> > and how many retries the client will make within that time. Indirectly
> > that will configure the time the client waits for each member before trying
> > to connect to the next member of the group.
> >
> > Art
> >
> > Art S. Kagel
> > Advanced DataTools (www.advancedatatools.com)
> > Blog: http://informix-myview.blogspot.com/
> >
> > Disclaimer: Please keep in mind that my own opinions are my own opinions
> > and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> > other organization with which I am associated either explicitly,
> > implicitly, or by inference. Neither do those opinions reflect those of
> > other individuals affiliated with any entity with which I am affiliated nor
> > those of the entities themselves.
> >
> > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
> > jkillen@allamericanasphalt.com> wrote:
> >
> > > I have 3 connection manager (Linux) instances whose SLA's are in a group
> > in
> > > sqlhosts (group option c=1). When I run dbaccess on any of those
> > machines,
> > > the
> > > SLA group is listed as an option, and I can connect to the group (it will
> > > round-robin my connection to one of the connection managers).
> > > Now that it is working on the servers themselves, I'd like to get it to
> > > work
> > > on my windows PC. I've added the SLA for each server as well as the SLA
> > > group
> > > into the system via Setnet32. When creating an ODBC connection, I'm using
> > > the
> > > following information:
> > >
> > > Server Name: sla_cm_grp
> > > Host Name: -
> > > Service: -
> > > Protocol: group
> > > Options: c=1
> > >
> > > When I try to test the connection, I get the error:
> > > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not
> > listed
> > > as
> > > a dbserver name in sqlhosts"
> > > If I use any of the connection managers directly I can connect just
> > fine, I
> > > just can't get it to connect to the group. Is this option supported by
> > the
> > > ODBC framework?
> > >
> > > I'm using CSDK version 3.50 TC8 on the windows machine. Server is running
> > > on
> > > Linux, Informix 12.1
> > >
> > > -Justin
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
*******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> > --089e013d1a4a91d12904de834cd0
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --089e01493c1ea0be0604de84f9f1
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply@@DQ
CM can't do round-robin connection or at least it couldn't in 11.7x -
which is a real PITA is your app layer starts up, makes lots of
connections before doing any real work - you end up with 90% of your
connections on a single machine
Cheers
Paul
> Hello.
> Supposing you have a group of servers, it should randomly connect to all
> of
> them.
> For more information, our friend Fernando Nunes has made a complete
> article
> about sqlhosts features, check it out:
>
>
http://informix-technology.blogspot.com.br/2013/08/sqlhosts-options-opcoes-do-sq
lhosts.html
>
> Regards.
>
> Alexandre Marini
> IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10
>
> IBM Information Management Informix Technical Professional
>
> IBM Infosphere DataStage Technical Professional
> Informix Senior DBA - Orizon Brasil
> BRIUG website administrator
> Informix independent consultant
>
>> To: ids@iiug.org
>> From: jkillen@allamericanasphalt.com
>> Subject: RE: windows odbc connection to connection mana.... [31089]
>> Date: Thu, 8 Aug 2013 13:10:54 -0400
>>
>> Does the c=1 option work for the windows CSDK 3.50.TC5? I have the
>> option
>> listed in the group registry key, but always seems to go back to the
>> same
>> server (the first one alphabetically).
>>
>> -Justin
>> -----Original Message-----
>> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
>> Art
>> Kagel
>> Sent: Thursday, June 06, 2013 4:50 PM
>> To: ids@iiug.org
>> Subject: Re: windows odbc connection to connection mana.... [30450]
>>
>> You are almost right, c=1 means that instead of every client connecting
>> in
>> the specified order starting with the first listed connection name each
>> client selects one of the connection names at random then cycles through
>> the list if the first one it tries doesn't respond. Not exactly round
>> robin, but it does do some load distribution if not balancing.
>>
>> Art
>>
>> Art S. Kagel
>> Advanced DataTools (www.advancedatatools.com)
>> Blog: http://informix-myview.blogspot.com/
>>
>> Disclaimer: Please keep in mind that my own opinions are my own opinions
>> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
>> other organization with which I am associated either explicitly,
>> implicitly, or by inference. Neither do those opinions reflect those of
>> other individuals affiliated with any entity with which I am affiliated
>> nor
>> those of the entities themselves.
>>
>> On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
>> jkillen@allamericanasphalt.com> wrote:
>>
>> > Art,
>> >
>> > Thanks - that works great! I think when we deploy the connection setup
>> to
>> > the
>> > client machines we'll be using registry files anyway, so requiring a
>> few
>> > extra
>> > keys is no big deal.
>> >
>> > As for the round-robin, I was under the impression that the option
>> "c=1"
>> > setup
>> > servers for round-robin distribution, but perhaps I'm mistaken.
> Round-robin
>> > connections to the CM's isn't a requirement for us, so it's not
>> something
>> > I'm
>> > going to worry about.
>> >
>> > -Justin
>> >
>> > -----Original Message-----
>> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
>> Art
>> > Kagel
>> > Sent: Thursday, June 06, 2013 2:50 PM
>> > To: ids@iiug.org
>> > Subject: Re: windows odbc connection to connection mana.... [30448]
>> >
>> > Justin:
>> >
>> > See this link for how to configure windows apps to use sqlhsots
>> "groups":
>> >
>> > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
>> >
>> > You have to manually edit the registry to enter the definition of the
> group
>> > since there is no sqlhosts file on the windows side.
>> >
>> > Also, AFAIK, using groups does not round robin through the group
>> members,
>> > it just sequentially tries each group member, in the order they are
> listed,
>> > until one of them responds. Groups are for failover not load balancing
>> > (hence the need for Connection Manager). You can make it kind of
>> > round-robin/load-balancing by using the environment variables
>> > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the
>> client
>> > will wait for a response from SOME group member before returning an
>> error
>> > and how many retries the client will make within that time. Indirectly
>> > that will configure the time the client waits for each member before
> trying
>> > to connect to the next member of the group.
>> >
>> > Art
>> >
>> > Art S. Kagel
>> > Advanced DataTools (www.advancedatatools.com)
>> > Blog: http://informix-myview.blogspot.com/
>> >
>> > Disclaimer: Please keep in mind that my own opinions are my own
>> opinions
>> > and do not reflect on my employer, Advanced DataTools, the IIUG, nor
>> any
>> > other organization with which I am associated either explicitly,
>> > implicitly, or by inference. Neither do those opinions reflect those
>> of
>> > other individuals affiliated with any entity with which I am
>> affiliated
> nor
>> > those of the entities themselves.
>> >
>> > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
>> > jkillen@allamericanasphalt.com> wrote:
>> >
>> > > I have 3 connection manager (Linux) instances whose SLA's are in a
>> group
>> > in
>> > > sqlhosts (group option c=1). When I run dbaccess on any of those
>> > machines,
>> > > the
>> > > SLA group is listed as an option, and I can connect to the group (it
> will
>> > > round-robin my connection to one of the connection managers).
>> > > Now that it is working on the servers themselves, I'd like to get it
>> to
>> > > work
>> > > on my windows PC. I've added the SLA for each server as well as the
>> SLA
>> > > group
>> > > into the system via Setnet32. When creating an ODBC connection, I'm
> using
>> > > the
>> > > following information:
>> > >
>> > > Server Name: sla_cm_grp
>> > > Host Name: -
>> > > Service: -
>> > > Protocol: group
>> > > Options: c=1
>> > >
>> > > When I try to test the connection, I get the error:
>> > > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not
>> > listed
>> > > as
>> > > a dbserver name in sqlhosts"
>> > > If I use any of the connection managers directly I can connect just
>> > fine, I
>> > > just can't get it to connect to the group. Is this option supported
>> by
>> > the
>> > > ODBC framework?
>> > >
>> > > I'm using CSDK version 3.50 TC8 on the windows machine. Server is
> running
>> > > on
>> > > Linux, Informix 12.1
>> > >
>> > > -Justin
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>> >
>>
>>
>
*******************************************************************************
>> > > Forum Note: Use "Reply" to post a response in the discussion forum.
>> > >
>> > >
>> >
>> > --089e013d1a4a91d12904de834cd0
>> >
>> >
>> >
>> >
>>
>>
>
*************************************
Perhaps I should clarify. Once I'm connected to the connection manager, the
connection manager redirects as expected (all our secondary servers are
read/write). To avoid a single point of failure, we have the connection
manager running on each of the servers. My problem is that on windows CSDK
3.5TC5 a connection to the SLA group always goes to the same connection
manager instead of randomly choosing an entry from the group (as per the c=1
option). We have a bit of a mix with the CSDK versions, ranging from 3.5TC5 to
3.5TC9; I'm just trying to find out if the c=1 option is supported, and if so,
what version it was added in (it seems to not work in TC5).
-Justin
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art Kagel
Sent: Thursday, August 08, 2013 10:18 AM
To: ids@iiug.org
Subject: Re: windows odbc connection to connection mana.... [31090]
Hmm, don't know. One thing to note: Groups will never failover to a
secondary that is read-only (just found this one out yesterday). This was
a change to the behavior of groups somewhere around v11.10 of the server
(so v3.10 of the CSDK). So, could that be the problem you are seeing?
Also, I don't remember when the c=1 option was first available (don't
think that it goes all the way back) so the CSDK/iConnect on your Windows
boxes may not support this if they are older. IBM can research that one
for you if your version on windows isn't up to snuff. Looking back I see
you said you are using v3.50.TC8 and that SHOULD be good, but again, not
sure.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
On Thu, Aug 8, 2013 at 1:10 PM, Justin Killen <
jkillen@allamericanasphalt.com> wrote:
> Does the c=1 option work for the windows CSDK 3.50.TC5? I have the option
> listed in the group registry key, but always seems to go back to the same
> server (the first one alphabetically).
>
> -Justin
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Thursday, June 06, 2013 4:50 PM
> To: ids@iiug.org
> Subject: Re: windows odbc connection to connection mana.... [30450]
>
> You are almost right, c=1 means that instead of every client connecting in
> the specified order starting with the first listed connection name each
> client selects one of the connection names at random then cycles through
> the list if the first one it tries doesn't respond. Not exactly round
> robin, but it does do some load distribution if not balancing.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> other organization with which I am associated either explicitly,
> implicitly, or by inference. Neither do those opinions reflect those of
> other individuals affiliated with any entity with which I am affiliated nor
> those of the entities themselves.
>
> On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
> jkillen@allamericanasphalt.com> wrote:
>
> > Art,
> >
> > Thanks - that works great! I think when we deploy the connection setup to
> > the
> > client machines we'll be using registry files anyway, so requiring a few
> > extra
> > keys is no big deal.
> >
> > As for the round-robin, I was under the impression that the option "c=1"
> > setup
> > servers for round-robin distribution, but perhaps I'm mistaken.
> Round-robin
> > connections to the CM's isn't a requirement for us, so it's not something
> > I'm
> > going to worry about.
> >
> > -Justin
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Art
> > Kagel
> > Sent: Thursday, June 06, 2013 2:50 PM
> > To: ids@iiug.org
> > Subject: Re: windows odbc connection to connection mana.... [30448]
> >
> > Justin:
> >
> > See this link for how to configure windows apps to use sqlhsots "groups":
> >
> > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
> >
> > You have to manually edit the registry to enter the definition of the
> group
> > since there is no sqlhosts file on the windows side.
> >
> > Also, AFAIK, using groups does not round robin through the group members,
> > it just sequentially tries each group member, in the order they are
> listed,
> > until one of them responds. Groups are for failover not load balancing
> > (hence the need for Connection Manager). You can make it kind of
> > round-robin/load-balancing by using the environment variables
> > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client
> > will wait for a response from SOME group member before returning an error
> > and how many retries the client will make within that time. Indirectly
> > that will configure the time the client waits for each member before
> trying
> > to connect to the next member of the group.
> >
> > Art
> >
> > Art S. Kagel
> > Advanced DataTools (www.advancedatatools.com)
> > Blog: http://informix-myview.blogspot.com/
> >
> > Disclaimer: Please keep in mind that my own opinions are my own opinions
> > and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> > other organization with which I am associated either explicitly,
> > implicitly, or by inference. Neither do those opinions reflect those of
> > other individuals affiliated with any entity with which I am affiliated
> nor
> > those of the entities themselves.
> >
> > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
> > jkillen@allamericanasphalt.com> wrote:
> >
> > > I have 3 connection manager (Linux) instances whose SLA's are in a
> group
> > in
> > > sqlhosts (group option c=1). When I run dbaccess on any of those
> > machines,
> > > the
> > > SLA group is listed as an option, and I can connect to the group (it
> will
> > > round-robin my connection to one of the connection managers).
> > > Now that it is working on the servers themselves, I'd like to get it to
> > > work
> > > on my windows PC. I've added the SLA for each server as well as the SLA
> > > group
> > > into the system via Setnet32. When creating an ODBC connection, I'm
> using
> > > the
> > > following information:
> > >
> > > Server Name: sla_cm_grp
> > > Host Name: -
> > > Service: -
> > > Protocol: group
> > > Options: c=1
> > >
> > > When I try to test the connection, I get the error:
> > > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not
> > listed
> > > as
> > > a dbserver name in sqlhosts"
> > > If I
Alexandre,
I have two problems with that article:
1) It is explaining how to setup a sqlhosts file, which windows doesn't use
(Art provided a link earlier in the tread for an IBM doc that explains how to
set it up on a windows system)
2) It doesn't specify a minimum CSDK version
-Justin
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Alexandre Marini
Sent: Thursday, August 08, 2013 10:24 AM
To: ids@iiug.org
Subject: RE: windows odbc connection to connection mana.... [31091]
Hello.
Supposing you have a group of servers, it should randomly connect to all of
them.
For more information, our friend Fernando Nunes has made a complete article
about sqlhosts features, check it out:
http://informix-technology.blogspot.com.br/2013/08/sqlhosts-options-opcoes-do-sq
lhosts.html
Regards.
Alexandre Marini
IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10
IBM Information Management Informix Technical Professional
IBM Infosphere DataStage Technical Professional
Informix Senior DBA - Orizon Brasil
BRIUG website administrator
Informix independent consultant
> To: ids@iiug.org
> From: jkillen@allamericanasphalt.com
> Subject: RE: windows odbc connection to connection mana.... [31089]
> Date: Thu, 8 Aug 2013 13:10:54 -0400
>
> Does the c=1 option work for the windows CSDK 3.50.TC5? I have the option
> listed in the group registry key, but always seems to go back to the same
> server (the first one alphabetically).
>
> -Justin
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Thursday, June 06, 2013 4:50 PM
> To: ids@iiug.org
> Subject: Re: windows odbc connection to connection mana.... [30450]
>
> You are almost right, c=1 means that instead of every client connecting in
> the specified order starting with the first listed connection name each
> client selects one of the connection names at random then cycles through
> the list if the first one it tries doesn't respond. Not exactly round
> robin, but it does do some load distribution if not balancing.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> other organization with which I am associated either explicitly,
> implicitly, or by inference. Neither do those opinions reflect those of
> other individuals affiliated with any entity with which I am affiliated nor
> those of the entities themselves.
>
> On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
> jkillen@allamericanasphalt.com> wrote:
>
> > Art,
> >
> > Thanks - that works great! I think when we deploy the connection setup to
> > the
> > client machines we'll be using registry files anyway, so requiring a few
> > extra
> > keys is no big deal.
> >
> > As for the round-robin, I was under the impression that the option "c=1"
> > setup
> > servers for round-robin distribution, but perhaps I'm mistaken.
Round-robin
> > connections to the CM's isn't a requirement for us, so it's not something
> > I'm
> > going to worry about.
> >
> > -Justin
> >
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> > Kagel
> > Sent: Thursday, June 06, 2013 2:50 PM
> > To: ids@iiug.org
> > Subject: Re: windows odbc connection to connection mana.... [30448]
> >
> > Justin:
> >
> > See this link for how to configure windows apps to use sqlhsots "groups":
> >
> > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
> >
> > You have to manually edit the registry to enter the definition of the
group
> > since there is no sqlhosts file on the windows side.
> >
> > Also, AFAIK, using groups does not round robin through the group members,
> > it just sequentially tries each group member, in the order they are
listed,
> > until one of them responds. Groups are for failover not load balancing
> > (hence the need for Connection Manager). You can make it kind of
> > round-robin/load-balancing by using the environment variables
> > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client
> > will wait for a response from SOME group member before returning an error
> > and how many retries the client will make within that time. Indirectly
> > that will configure the time the client waits for each member before
trying
> > to connect to the next member of the group.
> >
> > Art
> >
> > Art S. Kagel
> > Advanced DataTools (www.advancedatatools.com)
> > Blog: http://informix-myview.blogspot.com/
> >
> > Disclaimer: Please keep in mind that my own opinions are my own opinions
> > and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> > other organization with which I am associated either explicitly,
> > implicitly, or by inference. Neither do those opinions reflect those of
> > other individuals affiliated with any entity with which I am affiliated
nor
> > those of the entities themselves.
> >
> > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
> > jkillen@allamericanasphalt.com> wrote:
> >
> > > I have 3 connection manager (Linux) instances whose SLA's are in a group
> > in
> > > sqlhosts (group option c=1). When I run dbaccess on any of those
> > machines,
> > > the
> > > SLA group is listed as an option, and I can connect to the group (it
will
> > > round-robin my connection to one of the connection managers).
> > > Now that it is working on the servers themselves, I'd like to get it to
> > > work
> > > on my windows PC. I've added the SLA for each server as well as the SLA
> > > group
> > > into the system via Setnet32. When creating an ODBC connection, I'm
using
> > > the
> > > following information:
> > >
> > > Server Name: sla_cm_grp
> > > Host Name: -
> > > Service: -
> > > Protocol: group
> > > Options: c=1
> > >
> > > When I try to test the connection, I get the error:
> > > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not
> > listed
> > > as
> > > a dbserver name in sqlhosts"
> > > If I use any of the connection managers directly I can connect just
> > fine, I
> > > just can't get it to connect to the group. Is this option supported by
> > the
> > > ODBC framework?
> > >
> > > I'm using CSDK version 3.50 TC8 on the windows machine. Server is
running
> > > on
> > > Linux, Informix 12.1
> > >
> > > -Justin
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
*******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> > --089e013d1a4a91d12904de834cd0
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" t
As per presentation at IIUG this year, CM can only do load balanced
connections - or that is what we were told
Cheers
Paul
> Perhaps I should clarify. Once I'm connected to the connection manager,
> the
> connection manager redirects as expected (all our secondary servers are
> read/write). To avoid a single point of failure, we have the connection
> manager running on each of the servers. My problem is that on windows CSDK
> 3.5TC5 a connection to the SLA group always goes to the same connection
> manager instead of randomly choosing an entry from the group (as per the
> c=1
> option). We have a bit of a mix with the CSDK versions, ranging from
> 3.5TC5 to
> 3.5TC9; I'm just trying to find out if the c=1 option is supported, and if
> so,
> what version it was added in (it seems to not work in TC5).
>
> -Justin
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Thursday, August 08, 2013 10:18 AM
> To: ids@iiug.org
> Subject: Re: windows odbc connection to connection mana.... [31090]
>
> Hmm, don't know. One thing to note: Groups will never failover to a
> secondary that is read-only (just found this one out yesterday). This was
> a change to the behavior of groups somewhere around v11.10 of the server
> (so v3.10 of the CSDK). So, could that be the problem you are seeing?
> Also, I don't remember when the c=1 option was first available (don't
> think that it goes all the way back) so the CSDK/iConnect on your Windows
> boxes may not support this if they are older. IBM can research that one
> for you if your version on windows isn't up to snuff. Looking back I see
> you said you are using v3.50.TC8 and that SHOULD be good, but again, not
> sure.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> other organization with which I am associated either explicitly,
> implicitly, or by inference. Neither do those opinions reflect those of
> other individuals affiliated with any entity with which I am affiliated
> nor
> those of the entities themselves.
>
> On Thu, Aug 8, 2013 at 1:10 PM, Justin Killen <
> jkillen@allamericanasphalt.com> wrote:
>
>> Does the c=1 option work for the windows CSDK 3.50.TC5? I have the
>> option
>> listed in the group registry key, but always seems to go back to the
>> same
>> server (the first one alphabetically).
>>
>> -Justin
>> -----Original Message-----
>> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
>> Art
>> Kagel
>> Sent: Thursday, June 06, 2013 4:50 PM
>> To: ids@iiug.org
>> Subject: Re: windows odbc connection to connection mana.... [30450]
>>
>> You are almost right, c=1 means that instead of every client connecting
>> in
>> the specified order starting with the first listed connection name each
>> client selects one of the connection names at random then cycles through
>> the list if the first one it tries doesn't respond. Not exactly round
>> robin, but it does do some load distribution if not balancing.
>>
>> Art
>>
>> Art S. Kagel
>> Advanced DataTools (www.advancedatatools.com)
>> Blog: http://informix-myview.blogspot.com/
>>
>> Disclaimer: Please keep in mind that my own opinions are my own opinions
>> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
>> other organization with which I am associated either explicitly,
>> implicitly, or by inference. Neither do those opinions reflect those of
>> other individuals affiliated with any entity with which I am affiliated
>> nor
>> those of the entities themselves.
>>
>> On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
>> jkillen@allamericanasphalt.com> wrote:
>>
>> > Art,
>> >
>> > Thanks - that works great! I think when we deploy the connection setup
>> to
>> > the
>> > client machines we'll be using registry files anyway, so requiring a
>> few
>> > extra
>> > keys is no big deal.
>> >
>> > As for the round-robin, I was under the impression that the option
>> "c=1"
>> > setup
>> > servers for round-robin distribution, but perhaps I'm mistaken.
>> Round-robin
>> > connections to the CM's isn't a requirement for us, so it's not
>> something
>> > I'm
>> > going to worry about.
>> >
>> > -Justin
>> >
>> > -----Original Message-----
>> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
>> Art
>> > Kagel
>> > Sent: Thursday, June 06, 2013 2:50 PM
>> > To: ids@iiug.org
>> > Subject: Re: windows odbc connection to connection mana.... [30448]
>> >
>> > Justin:
>> >
>> > See this link for how to configure windows apps to use sqlhsots
>> "groups":
>> >
>> > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
>> >
>> > You have to manually edit the registry to enter the definition of the
>> group
>> > since there is no sqlhosts file on the windows side.
>> >
>> > Also, AFAIK, using groups does not round robin through the group
>> members,
>> > it just sequentially tries each group member, in the order they are
>> listed,
>> > until one of them responds. Groups are for failover not load balancing
>> > (hence the need for Connection Manager). You can make it kind of
>> > round-robin/load-balancing by using the environment variables
>> > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the
>> client
>> > will wait for a response from SOME group member before returning an
>> error
>> > and how many retries the client will make within that time. Indirectly
>> > that will configure the time the client waits for each member before
>> trying
>> > to connect to the next member of the group.
>> >
>> > Art
>> >
>> > Art S. Kagel
>> > Advanced DataTools (www.advancedatatools.com)
>> > Blog: http://informix-myview.blogspot.com/
>> >
>> > Disclaimer: Please keep in mind that my own opinions are my own
>> opinions
>> > and do not reflect on my employer, Advanced DataTools, the IIUG, nor
>> any
>> > other organization with which I am associated either explicitly,
>> > implicitly, or by inference. Neither do those opinions reflect those
>> of
>> > other individuals affiliated with any entity with which I am
>> affiliated
>> nor
>> > those of the entities themselves.
>> >
>> > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
>> > jkillen@allamericanasphalt.com> wrote:
>> >
>> > > I have 3 connection manager (Linux) instances whose SLA's are in a
>> group
>> > in
>> > > sqlhosts (group option c=1). When I run dbaccess on any of those
>> > machines,
>> > > the
>> > > SLA group is listed as an option, and I can connect to the group (it
>> will
>> > > round-robin my connection to one of the connection managers).
>> > > Now that it is working on the servers themselves, I'd like to get it
>> to
>> > > work
>> > > on my windows PC. I've added the SLA for each server as well as the
>> SLA
>>
It's not the CM behavior that I'm concerned with, it's the SQL group behavior.
For instance, given this sqlhosts, where each entry is a connection manager
SLA:
cm_hq group - - i=1777,c=1
cm_hq_srv1net onsoctcp srv1 cmhqsoc g=cm_hq
cm_hq_srv2net onsoctcp srv2 cmhqsoc g=cm_hq
cm_hq_srv3net onsoctcp srv3 cmhqsoc g=cm_hq
cm_hq_srv4net onsoctcp srv4 cmhqsoc g=cm_hq
cm_hq_srv5net onsoctcp srv5 cmhqsoc g=cm_hq
On my unix boxes, I can set INFORMIXSERVER=cm_hq and every time I attempt to
connect (dbaccess) I get assigned to a random connection manager (as monitored
in the connection manager logs for each server).
On my windows boxes, I have the registry keys setup as per IBM's document
(Art's link). In the branch node for the cm_hq group, I have the string value:
OPTIONS: i=1777,c=1
And yet, when I attempt to connect to cm_hq (with the .net provider), it
always connects to the first connection manager, as though the c=1 option was
not set.
So then, my question is - does the windows CSDK support the c=1 option on
groups, and if so as of which version?
-Justin
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Paul
Watson
Sent: Thursday, August 08, 2013 10:40 AM
To: ids@iiug.org
Subject: RE: windows odbc connection to connection mana.... [31096]
As per presentation at IIUG this year, CM can only do load balanced
connections - or that is what we were told
Cheers
Paul
> Perhaps I should clarify. Once I'm connected to the connection manager,
> the
> connection manager redirects as expected (all our secondary servers are
> read/write). To avoid a single point of failure, we have the connection
> manager running on each of the servers. My problem is that on windows CSDK
> 3.5TC5 a connection to the SLA group always goes to the same connection
> manager instead of randomly choosing an entry from the group (as per the
> c=1
> option). We have a bit of a mix with the CSDK versions, ranging from
> 3.5TC5 to
> 3.5TC9; I'm just trying to find out if the c=1 option is supported, and if
> so,
> what version it was added in (it seems to not work in TC5).
>
> -Justin
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Thursday, August 08, 2013 10:18 AM
> To: ids@iiug.org
> Subject: Re: windows odbc connection to connection mana.... [31090]
>
> Hmm, don't know. One thing to note: Groups will never failover to a
> secondary that is read-only (just found this one out yesterday). This was
> a change to the behavior of groups somewhere around v11.10 of the server
> (so v3.10 of the CSDK). So, could that be the problem you are seeing?
> Also, I don't remember when the c=1 option was first available (don't
> think that it goes all the way back) so the CSDK/iConnect on your Windows
> boxes may not support this if they are older. IBM can research that one
> for you if your version on windows isn't up to snuff. Looking back I see
> you said you are using v3.50.TC8 and that SHOULD be good, but again, not
> sure.
>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> Blog: http://informix-myview.blogspot.com/
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
> other organization with which I am associated either explicitly,
> implicitly, or by inference. Neither do those opinions reflect those of
> other individuals affiliated with any entity with which I am affiliated
> nor
> those of the entities themselves.
>
> On Thu, Aug 8, 2013 at 1:10 PM, Justin Killen <
> jkillen@allamericanasphalt.com> wrote:
>
>> Does the c=1 option work for the windows CSDK 3.50.TC5? I have the
>> option
>> listed in the group registry key, but always seems to go back to the
>> same
>> server (the first one alphabetically).
>>
>> -Justin
>> -----Original Message-----
>> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
>> Art
>> Kagel
>> Sent: Thursday, June 06, 2013 4:50 PM
>> To: ids@iiug.org
>> Subject: Re: windows odbc connection to connection mana.... [30450]
>>
>> You are almost right, c=1 means that instead of every client connecting
>> in
>> the specified order starting with the first listed connection name each
>> client selects one of the connection names at random then cycles through
>> the list if the first one it tries doesn't respond. Not exactly round
>> robin, but it does do some load distribution if not balancing.
>>
>> Art
>>
>> Art S. Kagel
>> Advanced DataTools (www.advancedatatools.com)
>> Blog: http://informix-myview.blogspot.com/
>>
>> Disclaimer: Please keep in mind that my own opinions are my own opinions
>> and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
>> other organization with which I am associated either explicitly,
>> implicitly, or by inference. Neither do those opinions reflect those of
>> other individuals affiliated with any entity with which I am affiliated
>> nor
>> those of the entities themselves.
>>
>> On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
>> jkillen@allamericanasphalt.com> wrote:
>>
>> > Art,
>> >
>> > Thanks - that works great! I think when we deploy the connection setup
>> to
>> > the
>> > client machines we'll be using registry files anyway, so requiring a
>> few
>> > extra
>> > keys is no big deal.
>> >
>> > As for the round-robin, I was under the impression that the option
>> "c=1"
>> > setup
>> > servers for round-robin distribution, but perhaps I'm mistaken.
>> Round-robin
>> > connections to the CM's isn't a requirement for us, so it's not
>> something
>> > I'm
>> > going to worry about.
>> >
>> > -Justin
>> >
>> > -----Original Message-----
>> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
>> Art
>> > Kagel
>> > Sent: Thursday, June 06, 2013 2:50 PM
>> > To: ids@iiug.org
>> > Subject: Re: windows odbc connection to connection mana.... [30448]
>> >
>> > Justin:
>> >
>> > See this link for how to configure windows apps to use sqlhsots
>> "groups":
>> >
>> > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
>> >
>> > You have to manually edit the registry to enter the definition of the
>> group
>> > since there is no sqlhosts file on the windows side.
>> >
>> > Also, AFAIK, using groups does not round robin through the group
>> members,
>> > it just sequentially tries each group member, in the order they are
>> listed,
>> > until one of them responds. Groups are for failover not load balancing
>> > (hence the need for Connection Manager). You can make it kind of
>> > round-robin/load-balancing by using the environment variables
>> > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the
>> client
>> > will wait for a response from SOME group member before returning an
>> error
>> > and how many retries the client will make within that time. Indirectly
>> > that will configure the time the client
Alexandre,
A new feature of 12.10 windows server is that it can utilize the informix
sqlhost file.
John F. Miller III
STSM, Lead Architect
miller3@us.ibm.com
503-747-1366
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 08/08/2013 10:39:20 AM:
> From: "Justin Killen" <jkillen@allamericanasphalt.com>
> To: ids@iiug.org,
> Date: 08/08/2013 11:16 AM
> Subject: RE: windows odbc connection to connection mana.... [31095]
> Sent by: ids-bounces@iiug.org
>
> Alexandre,
>
> I have two problems with that article:
> 1) It is explaining how to setup a sqlhosts file, which windows doesn't
use
> (Art provided a link earlier in the tread for an IBM doc that explains
how to
> set it up on a windows system)
> 2) It doesn't specify a minimum CSDK version
>
> -Justin
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Alexandre Marini
> Sent: Thursday, August 08, 2013 10:24 AM
> To: ids@iiug.org
> Subject: RE: windows odbc connection to connection mana.... [31091]
>
> Hello.
> Supposing you have a group of servers, it should randomly connect to all
of
> them.
> For more information, our friend Fernando Nunes has made a complete
article
> about sqlhosts features, check it out:
>
>
> http://informix-technology.blogspot.com.br/2013/08/sqlhosts-options-
> opcoes-do-sqlhosts.html
>
> Regards.
>
> Alexandre Marini
> IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10
>
> IBM Information Management Informix Technical Professional
>
> IBM Infosphere DataStage Technical Professional
> Informix Senior DBA - Orizon Brasil
> BRIUG website administrator
> Informix independent consultant
>
> > To: ids@iiug.org
> > From: jkillen@allamericanasphalt.com
> > Subject: RE: windows odbc connection to connection mana.... [31089]
> > Date: Thu, 8 Aug 2013 13:10:54 -0400
> >
> > Does the c=1 option work for the windows CSDK 3.50.TC5? I have the
option
> > listed in the group registry key, but always seems to go back to the
same
> > server (the first one alphabetically).
> >
> > -Justin
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Art
> > Kagel
> > Sent: Thursday, June 06, 2013 4:50 PM
> > To: ids@iiug.org
> > Subject: Re: windows odbc connection to connection mana.... [30450]
> >
> > You are almost right, c=1 means that instead of every client connecting
in
> > the specified order starting with the first listed connection name each
> > client selects one of the connection names at random then cycles
through
> > the list if the first one it tries doesn't respond. Not exactly round
> > robin, but it does do some load distribution if not balancing.
> >
> > Art
> >
> > Art S. Kagel
> > Advanced DataTools (www.advancedatatools.com)
> > Blog: http://informix-myview.blogspot.com/
> >
> > Disclaimer: Please keep in mind that my own opinions are my own
opinions
> > and do not reflect on my employer, Advanced DataTools, the IIUG, nor
any
> > other organization with which I am associated either explicitly,
> > implicitly, or by inference. Neither do those opinions reflect those of
> > other individuals affiliated with any entity with which I am affiliated
nor
> > those of the entities themselves.
> >
> > On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen <
> > jkillen@allamericanasphalt.com> wrote:
> >
> > > Art,
> > >
> > > Thanks - that works great! I think when we deploy the connectionsetup
to
> > > the
> > > client machines we'll be using registry files anyway, so requiring a
few
> > > extra
> > > keys is no big deal.
> > >
> > > As for the round-robin, I was under the impression that the option
"c=1"
> > > setup
> > > servers for round-robin distribution, but perhaps I'm mistaken.
> Round-robin
> > > connections to the CM's isn't a requirement for us, so it's not
something
> > > I'm
> > > going to worry about.
> > >
> > > -Justin
> > >
> > > -----Original Message-----
> > > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Art
> > > Kagel
> > > Sent: Thursday, June 06, 2013 2:50 PM
> > > To: ids@iiug.org
> > > Subject: Re: windows odbc connection to connection mana.... [30448]
> > >
> > > Justin:
> > >
> > > See this link for how to configure windows apps to use sqlhsots
"groups":
> > >
> > > http://www-01.ibm.com/support/docview.wss?uid=swg21447622
> > >
> > > You have to manually edit the registry to enter the definition of the
> group
> > > since there is no sqlhosts file on the windows side.
> > >
> > > Also, AFAIK, using groups does not round robin through the
groupmembers,
> > > it just sequentially tries each group member, in the order they are
> listed,
> > > until one of them responds. Groups are for failover not load
balancing
> > > (hence the need for Connection Manager). You can make it kind of
> > > round-robin/load-balancing by using the environment variables
> > > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the
client
> > > will wait for a response from SOME group member before returningan
error
> > > and how many retries the client will make within that time.
Indirectly
> > > that will configure the time the client waits for each member before
> trying
> > > to connect to the next member of the group.
> > >
> > > Art
> > >
> > > Art S. Kagel
> > > Advanced DataTools (www.advancedatatools.com)
> > > Blog: http://informix-myview.blogspot.com/
> > >
> > > Disclaimer: Please keep in mind that my own opinions are my own
opinions
> > > and do not reflect on my employer, Advanced DataTools, the IIUG, nor
any
> > > other organization with which I am associated either explicitly,
> > > implicitly, or by inference. Neither do those opinions reflect those
of
> > > other individuals affiliated with any entity with which I am
affiliated
> nor
> > > those of the entities themselves.
> > >
> > > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen <
> > > jkillen@allamericanasphalt.com> wrote:
> > >
> > > > I have 3 connection manager (Linux) instances whose SLA's are
> in a group
> > > in
> > > > sqlhosts (group option c=1). When I run dbaccess on any of those
> > > machines,
> > > > the
> > > > SLA group is listed as an option, and I can connect to the group
(it
> will
> > > > round-robin my connection to one of the connection managers).
> > > > Now that it is working on the servers themselves, I'd like to get
it to
> > > > work
> > > > on my windows PC. I've added the SLA for each server as well as the
SLA
> > > > group
> > > > into the system via Setnet32. When creating an ODBC connection, I'm
> using
> > > > the
> > > > following information:
> > > >
> > > > Server Name: sla_cm_grp
> > > > Host Name: -
> > > > Service: -
> > > > Protocol: group
> > > > Options: c=1
> > > >
> > > > When I try to test the connecti