Connection Manager - restrict connections
Tom runs Connection Manager on a separate box and wants it to use only one networked DBSERVERALIAS, but CM keeps enumerating and trying every alias in sqlhosts, including the shared-memory name and the HDR-only (s=6) entries, producing repeated -25539 'invalid connection-type' errors. Art asked about the SLA settings; theBP suggested an SLA option <dbserveraliases=off>, but Tom's test on CSDK 3.50.xC4 showed CM still adding all aliases, and theBP then conceded the option isn't actually present in that release, suggested using sqlhosts 'group' entries instead, and asked for the full primary/secondary/CM configuration. The thread ends with Tom posting his configuration; no confirmed fix is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Greetings all,
In a world where multiple DBSERVERALIAS values exist, is there a way
to restrict which ones the Connection Manager tries to establish
connections through?
As a brief example, If I have these values in the ONCONFIG file:
DBSERVERNAME aspbeL1
DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5
And given this sqlhosts file:
aspbeL1 onipcshm asp5 aspbeL1
aspbeL1_live onsoctcp asp5_be aspbeL1_livehdr1P_be onsoctcp asp5_be hdr1P_be s=6
odbc_asp5 onsoctcp asp5 odbc_asp5
NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
the same server.
The CM insists on trying to connect via the shared memory service
"aspbeL1", which it cannot because the CM is running on a separate
server.
What I want is for the CM to connect only to service aspbeL1_live. How
do I get the CM to ignore those other entries? It even tries to
connect to hdr1P_be even though the s=6 setting should (I believe) let
the CM know that only HDR-related traffic is allowed on this port.
Thanks,
Tom
What does the connection manager's SLA configuration look like? It should
only mention the networked servernames (hdr1P_be,aspbeL1_live,odbc_asp5)
Art
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. 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 Tue, May 12, 2009 at 1:57 PM, Tom <tlowrie@munis.com> wrote:
> Greetings all,
>
> In a world where multiple DBSERVERALIAS values exist, is there a way
> to restrict which ones the Connection Manager tries to establish
> connections through?
>
> As a brief example, If I have these values in the ONCONFIG file:
>
> DBSERVERNAME aspbeL1
> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>
> And given this sqlhosts file:
>
> aspbeL1 onipcshm asp5 aspbeL1
> aspbeL1_live onsoctcp asp5_be aspbeL1_live> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> odbc_asp5 onsoctcp asp5 odbc_asp5>
> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
> the same server.
>
> The CM insists on trying to connect via the shared memory service
> "aspbeL1", which it cannot because the CM is running on a separate
> server.
>
> What I want is for the CM to connect only to service aspbeL1_live. How
> do I get the CM to ignore those other entries? It even tries to
> connect to hdr1P_be even though the s=6 setting should (I believe) let
> the CM know that only HDR-related traffic is allowed on this port.
>
> Thanks,
>
> Tom
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
Tom wrote:
> Greetings all,
>
> In a world where multiple DBSERVERALIAS values exist, is there a way
> to restrict which ones the Connection Manager tries to establish
> connections through?
>
> As a brief example, If I have these values in the ONCONFIG file:
>
> DBSERVERNAME aspbeL1
> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>
> And given this sqlhosts file:
>
> aspbeL1 onipcshm asp5 aspbeL1
> aspbeL1_live onsoctcp asp5_be aspbeL1_live> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> odbc_asp5 onsoctcp asp5 odbc_asp5>
> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
> the same server.
>
> The CM insists on trying to connect via the shared memory service
> "aspbeL1", which it cannot because the CM is running on a separate
> server.
>
> What I want is for the CM to connect only to service aspbeL1_live. How
> do I get the CM to ignore those other entries? It even tries to
> connect to hdr1P_be even though the s=6 setting should (I believe) let
> the CM know that only HDR-related traffic is allowed on this port.
>
> Thanks,
>
> Tom
>
Well, depends on the version - i.e. the latest version from CSDK 3.50.xC4 has the option against the SLAs for <dbserveralias=off>
SLA oltp=((aspbeL1_live) <dbserveraliases=off>)
I suggest you also consider the latest engine 11.50.xC4 to go along with CSDK 3.50.xC4, quite a few "changes".
On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote:
> Tom wrote:
> > Greetings all,
>
> > In a world where multiple DBSERVERALIAS values exist, is there a way
> > to restrict which ones the Connection Manager tries to establish
> > connections through?
>
> > As a brief example, If I have these values in the ONCONFIG file:
>
> > DBSERVERNAME aspbeL1
> > DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>
> > And given this sqlhosts file:
>
> > aspbeL1 onipcshm asp5 aspbeL1
> > aspbeL1_live onsoctcp asp5_be aspbeL1_live> > hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> > odbc_asp5 onsoctcp asp5 odbc_asp5>
> > NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
> > the same server.
>
> > The CM insists on trying to connect via the shared memory service
> > "aspbeL1", which it cannot because the CM is running on a separate
> > server.
>
> > What I want is for the CM to connect only to service aspbeL1_live. How
> > do I get the CM to ignore those other entries? It even tries to
> > connect to hdr1P_be even though the s=6 setting should (I believe) let
> > the CM know that only HDR-related traffic is allowed on this port.
>
> > Thanks,
>
> > Tom
>
> Well, depends on the version - i.e. the latest version from CSDK 3.50.xC4 has the option against the SLAs for <dbserveralias=off>
>
> SLA oltp=((aspbeL1_live) <dbserveraliases=off>)
>
> I suggest you also consider the latest engine 11.50.xC4 to go along with CSDK 3.50.xC4, quite a few "changes".- Hide quoted text -
>
> - Show quoted text -
This is very interesting. I thought that the values to the right of
the equals sign in the SLA statements were pre-defined constants, like
HDR, SDS, primary, etc. Can you point me in the direction of any
documentation that shows your type of example?
I'll test the SLA defined as you show next.
Thanks,
Tom
On May 12, 3:05 pm, Tom <tlow...@munis.com> wrote:
> On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote:
>
>
>
>
>
> > Tom wrote:
> > > Greetings all,
>
> > > In a world where multiple DBSERVERALIAS values exist, is there a way
> > > to restrict which ones the Connection Manager tries to establish
> > > connections through?
>
> > > As a brief example, If I have these values in the ONCONFIG file:
>
> > > DBSERVERNAME aspbeL1
> > > DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>
> > > And given this sqlhosts file:
>
> > > aspbeL1 onipcshm asp5 aspbeL1
> > > aspbeL1_live onsoctcp asp5_be aspbeL1_live> > > hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> > > odbc_asp5 onsoctcp asp5 odbc_asp5>
> > > NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
> > > the same server.
>
> > > The CM insists on trying to connect via the shared memory service
> > > "aspbeL1", which it cannot because the CM is running on a separate
> > > server.
>
> > > What I want is for the CM to connect only to service aspbeL1_live. How
> > > do I get the CM to ignore those other entries? It even tries to
> > > connect to hdr1P_be even though the s=6 setting should (I believe) let
> > > the CM know that only HDR-related traffic is allowed on this port.
>
> > > Thanks,
>
> > > Tom
>
> > Well, depends on the version - i.e. the latest version from CSDK 3.50.xC4 has the option against the SLAs for <dbserveralias=off>
>
> > SLA oltp=((aspbeL1_live) <dbserveraliases=off>)
>
> > I suggest you also consider the latest engine 11.50.xC4 to go along with CSDK 3.50.xC4, quite a few "changes".- Hide quoted text -
>
> > - Show quoted text -
>
> This is very interesting. I thought that the values to the right of
> the equals sign in the SLA statements were pre-defined constants, like
> HDR, SDS, primary, etc. Can you point me in the direction of any
> documentation that shows your type of example?
>
> I'll test the SLA defined as you show next.
>
> Thanks,
>
> Tom- Hide quoted text -
>
> - Show quoted text -
I made the adjustments to the CM config file. Here it is:
NAME oncmsm_1
SLA oltp_cm1=((aspbeL1_live) <DBSERVERALIASES=OFF>)
SLA report_cm1=((hdr1_live) <DBSERVERALIASES=OFF>)
DEBUG 1
LOGFILE /usr/local/IDS/IBM_IDS/tmp/cmsm_1.log
FOC HDR,10
NOTE: I've tried using lower case as well as upper case with the same
results.
But, the CM still tries to use all possible connections. Here is the
log:
Wed May 13 08:22:10 2009
08:22:10 IBM Informix Connection Manager
08:22:10 Connection Manager name is oncmsm_1
08:22:10 Starting Connection Manager...
08:22:10 stat(/usr/local/IDS/IBM_IDS/etc/passwd_file) failed, errno =
2
08:22:10 Warning: Password Manager failed; working in trusted node
mode
08:22:10 Current max open fd is 2000
08:22:10 switch to daemon mode
08:22:10 new daemon pid is 115020
08:22:10 fcntl(/usr/local/IDS/IBM_IDS/tmp/cmsm.pid.oncmsm_1) success
errno = 0
08:22:10 dbservername = aspbeL1_live
08:22:10 nettype = onsoctcp
08:22:10 hostname = asp5_be
08:22:10 servicename = aspbeL1_live
08:22:10 options =
08:22:10 listener oltp_cm1 initializing
08:22:10 create new thread 772 for aspbeL1_live
08:22:10 CONNECT to sysmaster@aspbeL1_live|onsoctcp|asp5_be|
aspbeL1_live
08:22:10 listener report_cm1 initializing
08:22:10 Listener oltp_cm1=aspbeL1_live <dbserveraliases=off> is
active with 8 worker threads
08:22:10 Listener report_cm1=hdr1_live <dbserveraliases=off> is active
with 8 worker threads
08:22:10 CONNECT to sysmaster@aspbeL1_live|onsoctcp|asp5_be|
aspbeL1_live SQLCODE = (0,0,)
08:22:10 aspbeL1_live protocols = 1
08:22:10 adding aspbeL1_live alias hdr1P_be with protocol onsoctcp 1
08:22:10 adding aspbeL1_live alias aspbeL1 with protocol onipcshm 1
08:22:10 adding aspbeL1_live alias odbc_asp5 with protocol onsoctcp 1
08:22:10 fetch sysconfig_cursor sqlcode = (100,0,)
08:22:10 Connection Manager successfully connected to aspbeL1_live
08:22:10 Arbitrator FOC string = HDR,10
08:22:10 Arbitrator setting primary name = aspbeL1
08:22:10 FOC[0] = HDR
08:22:10 FOC timeout = 10
08:22:10 create new thread 5398 for hdr1S_be
08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
08:22:10 get aspbeL1_live CM_ADM event 8:3 oncmsm_1
08:22:10 Arbitrator received CM event, subtype=3, cm=oncmsm_1
08:22:10 Arbitrator reinitialized CM names
08:22:10 Arbitrator added CM name = oncmsm_1
08:22:10 Arbitrator is active on CM = oncmsm_1
08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
08:22:11 Connection Manager started successfully
08:22:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
08:22:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
08:22:22 get aspbeL1_live CM_ADM event 8:3 oncmsm_2
08:22:22 Arbitrator received CM event, subtype=3, cm=oncmsm_2
08:22:22 Arbitrator reinitialized CM names
08:22:22 Arbitrator added CM name = oncmsm_1
08:22:22 Arbitrator added CM name = oncmsm_2
08:22:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
08:22:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
08:22:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
08:22:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
08:22:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
08:22:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
08:23:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
08:23:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
Thanks,
Tom
Tom wrote:
> On May 12, 3:05 pm, Tom <tlow...@munis.com> wrote:
>> On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote:
>>
>>
>>
>>
>>
>>> Tom wrote:
>>>> Greetings all,
>>>> In a world where multiple DBSERVERALIAS values exist, is there a way
>>>> to restrict which ones the Connection Manager tries to establish
>>>> connections through?
>>>> As a brief example, If I have these values in the ONCONFIG file:
>>>> DBSERVERNAME aspbeL1
>>>> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>>>> And given this sqlhosts file:
>>>> aspbeL1 onipcshm asp5 aspbeL1
>>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live>>>> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
>>>> odbc_asp5 onsoctcp asp5 odbc_asp5>>>> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
>>>> the same server.
>>>> The CM insists on trying to connect via the shared memory service
>>>> "aspbeL1", which it cannot because the CM is running on a separate
>>>> server.
>>>> What I want is for the CM to connect only to service aspbeL1_live. How
>>>> do I get the CM to ignore those other entries? It even tries to
>>>> connect to hdr1P_be even though the s=6 setting should (I believe) let
>>>> the CM know that only HDR-related traffic is allowed on this port.
>>>> Thanks,
>>>> Tom
>>> Well, depends on the version - i.e. the latest version from CSDK 3.50.xC4 has the option against the SLAs for <dbserveralias=off>
>>> SLA oltp=((aspbeL1_live) <dbserveraliases=off>)
>>> I suggest you also consider the latest engine 11.50.xC4 to go along with CSDK 3.50.xC4, quite a few "changes".- Hide quoted text -
>>> - Show quoted text -
>> This is very interesting. I thought that the values to the right of
>> the equals sign in the SLA statements were pre-defined constants, like
>> HDR, SDS, primary, etc. Can you point me in the direction of any
>> documentation that shows your type of example?
>>
>> I'll test the SLA defined as you show next.
>>
>> Thanks,
>>
>> Tom- Hide quoted text -
>>
>> - Show quoted text -
>
> I made the adjustments to the CM config file. Here it is:
>
>
> NAME oncmsm_1
> SLA oltp_cm1=((aspbeL1_live) <DBSERVERALIASES=OFF>)
> SLA report_cm1=((hdr1_live) <DBSERVERALIASES=OFF>)
> DEBUG 1
> LOGFILE /usr/local/IDS/IBM_IDS/tmp/cmsm_1.log
> FOC HDR,10
>
> NOTE: I've tried using lower case as well as upper case with the same
> results.
>
> But, the CM still tries to use all possible connections. Here is the
> log:
>
> Wed May 13 08:22:10 2009
> 08:22:10 IBM Informix Connection Manager
> 08:22:10 Connection Manager name is oncmsm_1
> 08:22:10 Starting Connection Manager...
> 08:22:10 stat(/usr/local/IDS/IBM_IDS/etc/passwd_file) failed, errno =
> 2
> 08:22:10 Warning: Password Manager failed; working in trusted node
> mode
> 08:22:10 Current max open fd is 2000
> 08:22:10 switch to daemon mode
> 08:22:10 new daemon pid is 115020
> 08:22:10 fcntl(/usr/local/IDS/IBM_IDS/tmp/cmsm.pid.oncmsm_1) success
> errno = 0
> 08:22:10 dbservername = aspbeL1_live
> 08:22:10 nettype = onsoctcp
> 08:22:10 hostname = asp5_be
> 08:22:10 servicename = aspbeL1_live
> 08:22:10 options =
> 08:22:10 listener oltp_cm1 initializing
> 08:22:10 create new thread 772 for aspbeL1_live
> 08:22:10 CONNECT to sysmaster@aspbeL1_live|onsoctcp|asp5_be|
> aspbeL1_live
> 08:22:10 listener report_cm1 initializing
> 08:22:10 Listener oltp_cm1=aspbeL1_live <dbserveraliases=off> is
> active with 8 worker threads
> 08:22:10 Listener report_cm1=hdr1_live <dbserveraliases=off> is active
> with 8 worker threads
> 08:22:10 CONNECT to sysmaster@aspbeL1_live|onsoctcp|asp5_be|
> aspbeL1_live SQLCODE = (0,0,)
> 08:22:10 aspbeL1_live protocols = 1
> 08:22:10 adding aspbeL1_live alias hdr1P_be with protocol onsoctcp 1
> 08:22:10 adding aspbeL1_live alias aspbeL1 with protocol onipcshm 1
> 08:22:10 adding aspbeL1_live alias odbc_asp5 with protocol onsoctcp 1
> 08:22:10 fetch sysconfig_cursor sqlcode = (100,0,)
> 08:22:10 Connection Manager successfully connected to aspbeL1_live
> 08:22:10 Arbitrator FOC string = HDR,10
> 08:22:10 Arbitrator setting primary name = aspbeL1
> 08:22:10 FOC[0] = HDR
> 08:22:10 FOC timeout = 10
> 08:22:10 create new thread 5398 for hdr1S_be
> 08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> 08:22:10 get aspbeL1_live CM_ADM event 8:3 oncmsm_1
> 08:22:10 Arbitrator received CM event, subtype=3, cm=oncmsm_1
> 08:22:10 Arbitrator reinitialized CM names
> 08:22:10 Arbitrator added CM name = oncmsm_1
> 08:22:10 Arbitrator is active on CM = oncmsm_1
> 08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> SQLCODE = (-25539,0,)
> 08:22:11 Connection Manager started successfully
> 08:22:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> 08:22:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> SQLCODE = (-25539,0,)
> 08:22:22 get aspbeL1_live CM_ADM event 8:3 oncmsm_2
> 08:22:22 Arbitrator received CM event, subtype=3, cm=oncmsm_2
> 08:22:22 Arbitrator reinitialized CM names
> 08:22:22 Arbitrator added CM name = oncmsm_1
> 08:22:22 Arbitrator added CM name = oncmsm_2
> 08:22:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> 08:22:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> SQLCODE = (-25539,0,)
> 08:22:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> 08:22:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> SQLCODE = (-25539,0,)
> 08:22:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> 08:22:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> SQLCODE = (-25539,0,)
> 08:23:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> 08:23:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> SQLCODE = (-25539,0,)
>
>
> Thanks,
>
> Tom
What version of csdk are you using?
On May 13, 8:44 am, theBP <th...@Usenet-News.Net> wrote:
> Tom wrote:
> > On May 12, 3:05 pm, Tom <tlow...@munis.com> wrote:
> >> On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote:
>
> >>> Tom wrote:
> >>>> Greetings all,
> >>>> In a world where multiple DBSERVERALIAS values exist, is there a way
> >>>> to restrict which ones the Connection Manager tries to establish
> >>>> connections through?
> >>>> As a brief example, If I have these values in the ONCONFIG file:
> >>>> DBSERVERNAME aspbeL1
> >>>> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5> >>>> And given this sqlhosts file:
> >>>> aspbeL1 onipcshm asp5 aspbeL1
> >>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live> >>>> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> >>>> odbc_asp5 onsoctcp asp5 odbc_asp5> >>>> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
> >>>> the same server.
> >>>> The CM insists on trying to connect via the shared memory service
> >>>> "aspbeL1", which it cannot because the CM is running on a separate
> >>>> server.
> >>>> What I want is for the CM to connect only to service aspbeL1_live. How
> >>>> do I get the CM to ignore those other entries? It even tries to
> >>>> connect to hdr1P_be even though the s=6 setting should (I believe) let
> >>>> the CM know that only HDR-related traffic is allowed on this port.
> >>>> Thanks,
> >>>> Tom
> >>> Well, depends on the version - i.e. the latest version from CSDK 3.50.xC4 has the option against the SLAs for <dbserveralias=off>
> >>> SLA oltp=((aspbeL1_live) <dbserveraliases=off>)
> >>> I suggest you also consider the latest engine 11.50.xC4 to go along with CSDK 3.50.xC4, quite a few "changes".- Hide quoted text -
> >>> - Show quoted text -
> >> This is very interesting. I thought that the values to the right of
> >> the equals sign in the SLA statements were pre-defined constants, like
> >> HDR, SDS, primary, etc. Can you point me in the direction of any
> >> documentation that shows your type of example?
>
> >> I'll test the SLA defined as you show next.
>
> >> Thanks,
>
> >> Tom- Hide quoted text -
>
> >> - Show quoted text -
>
> > I made the adjustments to the CM config file. Here it is:
>
> > NAME oncmsm_1
> > SLA oltp_cm1=((aspbeL1_live) <DBSERVERALIASES=OFF>)
> > SLA report_cm1=((hdr1_live) <DBSERVERALIASES=OFF>)
> > DEBUG 1
> > LOGFILE /usr/local/IDS/IBM_IDS/tmp/cmsm_1.log
> > FOC HDR,10
>
> > NOTE: I've tried using lower case as well as upper case with the same
> > results.
>
> > But, the CM still tries to use all possible connections. Here is the
> > log:
>
> > Wed May 13 08:22:10 2009
> > 08:22:10 IBM Informix Connection Manager
> > 08:22:10 Connection Manager name is oncmsm_1
> > 08:22:10 Starting Connection Manager...
> > 08:22:10 stat(/usr/local/IDS/IBM_IDS/etc/passwd_file) failed, errno =
> > 2
> > 08:22:10 Warning: Password Manager failed; working in trusted node
> > mode
> > 08:22:10 Current max open fd is 2000
> > 08:22:10 switch to daemon mode
> > 08:22:10 new daemon pid is 115020
> > 08:22:10 fcntl(/usr/local/IDS/IBM_IDS/tmp/cmsm.pid.oncmsm_1) success
> > errno = 0
> > 08:22:10 dbservername = aspbeL1_live
> > 08:22:10 nettype = onsoctcp
> > 08:22:10 hostname = asp5_be
> > 08:22:10 servicename = aspbeL1_live
> > 08:22:10 options =
> > 08:22:10 listener oltp_cm1 initializing
> > 08:22:10 create new thread 772 for aspbeL1_live
> > 08:22:10 CONNECT to sysmaster@aspbeL1_live|onsoctcp|asp5_be|
> > aspbeL1_live
> > 08:22:10 listener report_cm1 initializing
> > 08:22:10 Listener oltp_cm1=aspbeL1_live <dbserveraliases=off> is
> > active with 8 worker threads
> > 08:22:10 Listener report_cm1=hdr1_live <dbserveraliases=off> is active
> > with 8 worker threads
> > 08:22:10 CONNECT to sysmaster@aspbeL1_live|onsoctcp|asp5_be|
> > aspbeL1_live SQLCODE = (0,0,)
> > 08:22:10 aspbeL1_live protocols = 1
> > 08:22:10 adding aspbeL1_live alias hdr1P_be with protocol onsoctcp 1
> > 08:22:10 adding aspbeL1_live alias aspbeL1 with protocol onipcshm 1
> > 08:22:10 adding aspbeL1_live alias odbc_asp5 with protocol onsoctcp 1
> > 08:22:10 fetch sysconfig_cursor sqlcode = (100,0,)
> > 08:22:10 Connection Manager successfully connected to aspbeL1_live
> > 08:22:10 Arbitrator FOC string = HDR,10
> > 08:22:10 Arbitrator setting primary name = aspbeL1
> > 08:22:10 FOC[0] = HDR
> > 08:22:10 FOC timeout = 10
> > 08:22:10 create new thread 5398 for hdr1S_be
> > 08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > 08:22:10 get aspbeL1_live CM_ADM event 8:3 oncmsm_1
> > 08:22:10 Arbitrator received CM event, subtype=3, cm=oncmsm_1
> > 08:22:10 Arbitrator reinitialized CM names
> > 08:22:10 Arbitrator added CM name = oncmsm_1
> > 08:22:10 Arbitrator is active on CM = oncmsm_1
> > 08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > SQLCODE = (-25539,0,)
> > 08:22:11 Connection Manager started successfully
> > 08:22:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > 08:22:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > SQLCODE = (-25539,0,)
> > 08:22:22 get aspbeL1_live CM_ADM event 8:3 oncmsm_2
> > 08:22:22 Arbitrator received CM event, subtype=3, cm=oncmsm_2
> > 08:22:22 Arbitrator reinitialized CM names
> > 08:22:22 Arbitrator added CM name = oncmsm_1
> > 08:22:22 Arbitrator added CM name = oncmsm_2
> > 08:22:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > 08:22:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > SQLCODE = (-25539,0,)
> > 08:22:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > 08:22:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > SQLCODE = (-25539,0,)
> > 08:22:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > 08:22:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > SQLCODE = (-25539,0,)
> > 08:23:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > 08:23:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
> > SQLCODE = (-25539,0,)
>
> > Thanks,
>
> > Tom
>
> What version of csdk are you using?- Hide quoted text -
>
> - Show quoted text -
3.50.xC4, April 2009
Tom wrote:
> On May 13, 8:44 am, theBP <th...@Usenet-News.Net> wrote:
>> Tom wrote:
>>> On May 12, 3:05 pm, Tom <tlow...@munis.com> wrote:
>>>> On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote:
>>>>> Tom wrote:
>>>>>> Greetings all,
>>>>>> In a world where multiple DBSERVERALIAS values exist, is there a way
>>>>>> to restrict which ones the Connection Manager tries to establish
>>>>>> connections through?
>>>>>> As a brief example, If I have these values in the ONCONFIG file:
>>>>>> DBSERVERNAME aspbeL1
>>>>>> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>>>>>> And given this sqlhosts file:
>>>>>> aspbeL1 onipcshm asp5 aspbeL1
>>>>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live>>>>>> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
>>>>>> odbc_asp5 onsoctcp asp5 odbc_asp5>>>>>> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
>>>>>> the same server.
>>>>>> The CM insists on trying to connect via the shared memory service
>>>>>> "aspbeL1", which it cannot because the CM is running on a separate
>>>>>> server.
>>>>>> What I want is for the CM to connect only to service aspbeL1_live. How
>>>>>> do I get the CM to ignore those other entries? It even tries to
>>>>>> connect to hdr1P_be even though the s=6 setting should (I believe) let
>>>>>> the CM know that only HDR-related traffic is allowed on this port.
>>>>>> Thanks,
>>>>>> Tom
Hi Tom,
Well, a few defects to be logged I feel :-/
1. dbserveralias=off is not present in 3.50.xC4
2. I would suggest that you consider using "group" syntax in your sqlhosts (note shared memory connection is not in the group):
aspbeL1 onipcshm asp5 aspbeL1
aspbel group - - i=1aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel
hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6
odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel
Really, the "group" should also include the actual HDR secondary, so that if you want to re-direct connections to the HDR secondary
you can.
3. What INFORMIXSERVER do you start connection manager with?
I suggest that you use either the "group" aspbel (although this appears to have issues :-/ ) or aspbeL1_live.
4. The is an error being generated when one of the Connection Manager tries to use :
hdr1P_be onsoctcp asp5_be hdr1P_be s=6
08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be SQLCODE = (-25539,0,)
which I think is for your HDR secondary
> finderr 25539
-25539 Invalid connection-type.
The connection-type is invalid for the database server. This message appears when
the database server is configured to address specific connection requests, for examplefor an
ER or HDR connection.
In order for me to (more easily) get a complete picture, can you fill in the blanks :
Primary :
=========
DBSERVERNAME aspbeL1
DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5
Secondary :
===========
DBSERVERNAME ??????DBSERVERALIAS ??????
sqlhosts
========
# Primary entries
aspbeL1 onipcshm asp5 aspbeL1
aspbel group - - i=1aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel
hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6
odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel
# Secondary entries
??????????
hdr1S_be onsoctcp asp6_be hdr1S_be g=aspbel
??????????
??????????
??????????
# Connection Manager SLA Entries
aspbeL1_live onsoctcp ???????
etc. etc.
Connection Manager INFORMIXSERVER env vars
==========================================
Connection Manager oncmsm_1 Config File :
=========================================
NAME oncmsm_1
SLA oltp_cm1=aspbeL1_live
SLA report_cm1=hdr1_live
????????????
LOGFILE (Hopefully separate to oncmsm_2)
Connection Manager oncmsm_2 Config File :
=========================================
NAME oncmsm_2
SLA ?????????????
SLA ?????????????
????????????????
LOGFILE (Hopefully separate to oncmsm_1)
If anything, we can at least get a load of issues logged :-/
On May 14, 4:57 am, theBP <th...@Usenet-News.Net> wrote:
> Tom wrote:
> > On May 13, 8:44 am, theBP <th...@Usenet-News.Net> wrote:
> >> Tom wrote:
> >>> On May 12, 3:05 pm, Tom <tlow...@munis.com> wrote:
> >>>> On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote:
> >>>>> Tom wrote:
> >>>>>> Greetings all,
> >>>>>> In a world where multiple DBSERVERALIAS values exist, is there a way
> >>>>>> to restrict which ones the Connection Manager tries to establish
> >>>>>> connections through?
> >>>>>> As a brief example, If I have these values in the ONCONFIG file:
> >>>>>> DBSERVERNAME aspbeL1
> >>>>>> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5> >>>>>> And given this sqlhosts file:
> >>>>>> aspbeL1 onipcshm asp5 aspbeL1
> >>>>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live> >>>>>> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> >>>>>> odbc_asp5 onsoctcp asp5 odbc_asp5> >>>>>> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
> >>>>>> the same server.
> >>>>>> The CM insists on trying to connect via the shared memory service
> >>>>>> "aspbeL1", which it cannot because the CM is running on a separate
> >>>>>> server.
> >>>>>> What I want is for the CM to connect only to service aspbeL1_live. How
> >>>>>> do I get the CM to ignore those other entries? It even tries to
> >>>>>> connect to hdr1P_be even though the s=6 setting should (I believe) let
> >>>>>> the CM know that only HDR-related traffic is allowed on this port.
> >>>>>> Thanks,
> >>>>>> Tom
>
> Hi Tom,
>
> Well, a few defects to be logged I feel :-/
>
> 1. dbserveralias=off is not present in 3.50.xC4
>
> 2. I would suggest that you consider using "group" syntax in your sqlhosts (note shared memory connection is not in the group):
>
> aspbeL1 onipcshm asp5 aspbeL1> aspbel group - - i=1
> aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel
> hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6
> odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel
>
> Really, the "group" should also include the actual HDR secondary, so that if you want to re-direct connections to the HDR secondary
> you can.
>
> 3. What INFORMIXSERVER do you start connection manager with?
>
> I suggest that you use either the "group" aspbel (although this appears to have issues :-/ ) or aspbeL1_live.
>
> 4. The is an error being generated when one of the Connection Manager tries to use :
>
> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
>
> 08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be SQLCODE = (-25539,0,)
>
> which I think is for your HDR secondary
>
> > finderr 25539
> -25539 Invalid connection-type.
>
> The connection-type is invalid for the database server. This message appears when
> the database server is configured to address specific connection requests, for examplefor an
> ER or HDR connection.
>
> In order for me to (more easily) get a complete picture, can you fill in the blanks :
>
> Primary :
> =========
> DBSERVERNAME aspbeL1
> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>
> Secondary :
> ===========
> DBSERVERNAME ??????> DBSERVERALIAS ??????
>
> sqlhosts
> ========
> # Primary entries
> aspbeL1 onipcshm asp5 aspbeL1> aspbel group - - i=1
> aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel
> hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6
> odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel
> # Secondary entries
> ??????????
> hdr1S_be onsoctcp asp6_be hdr1S_be g=aspbel
> ??????????
> ??????????
> ??????????
> # Connection Manager SLA Entries
> aspbeL1_live onsoctcp ???????
> etc. etc.
>
> Connection Manager INFORMIXSERVER env vars
> ==========================================
>
> Connection Manager oncmsm_1 Config File :
> =========================================
> NAME oncmsm_1
> SLA oltp_cm1=aspbeL1_live
> SLA report_cm1=hdr1_live
> ????????????
> LOGFILE (Hopefully separate to oncmsm_2)
>
> Connection Manager oncmsm_2 Config File :
> =========================================
> NAME oncmsm_2
> SLA ?????????????
> SLA ?????????????
> ????????????????
> LOGFILE (Hopefully separate to oncmsm_1)
>
> If anything, we can at least get a load of issues logged :-/- Hide quoted text -
>
> - Show quoted text -
Here is my configuration:
ASP5 is the primary server in an HDR pair. ASP6 is the secondary, or
HDR server in the pair.
Each server is connected to a private switch that also connects them
to the application server, which is ASP4. ASP4 is not part of the
MACH11 Cluster. Each server also connects to a routed switch, that is
accessible throughout our network. the "_be" in the host name
indicates "back end", which is the private switch connection.
The goal is to have the CM use ONLY aspbeL1_live and hdr1_live for
connections. Here is the desired connection usage:
Private switch connections:
aspbeL1_live: Primary. All CM managed connections go here.
hdr1_live: Secondary. If aspbeL1_live dies - promote to
active (normally HDR1 is read-only)
hdr1P_be: For HDR server to server traffic only (hence the s=6 value)
hdr1S_be: For HDR server to server traffic only (hence the s=6 value)
Routed switch connections:
odbc_asp5: To allow non-application server (ASP4) ODBC type
connections
munislive: To allow non-application server (ASP4) ODBC type
connections
Shared Memory connections:
aspbeL1: For internal use only.
hdr1: For internal use only.
Here are the ASP5 configuration values:
DBSERVERNAME: aspbeL1
DBSERVERALIASES: hdr1P_be, aspbeL1_live, odbc_asp5
sqlhosts file on ASP5:
# ASP5
aspbeL1 onipcshm asp5 aspbeL1# aspbeL1_live onsoctcp asp5_be aspbeL1_live
hdr1P_be onsoctcp asp5_be hdr1P_be s=6
odbc_asp5 onsoctcp asp5 odbc_asp5
# ASP6
# hdr1 onipcshm asp6 hdr1
# hdr1_live onsoctcp asp6_be hdr1_live
hdr1S_be onsoctcp asp6_be hdr1S_be s=6
munislive onsoctcp asp6 munislive
# ASP4 Programs connect via this group via the connection manager
g_mach group - - e=hdr1_live
aspbeL1_live onsoctcp asp5_be aspbeL1_live
g=g_mach
hdr1_live onsoctcp asp6_be hdr1_live
g=g_mach
# Connection Manager - ASP4 Programs
oltp group -
- e=oltp_cm2
oltp_cm1 onsoctcp asp5_be cmport1 g=oltp
oltp_cm2 onsoctcp asp6_be
On May 14, 11:47 am, Tom <tlow...@munis.com> wrote:
> On May 14, 4:57 am, theBP <th...@Usenet-News.Net> wrote:
>
>
>
>
>
> > Tom wrote:
> > > On May 13, 8:44 am, theBP <th...@Usenet-News.Net> wrote:
> > >> Tom wrote:
> > >>> On May 12, 3:05 pm, Tom <tlow...@munis.com> wrote:
> > >>>> On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote:
> > >>>>> Tom wrote:
> > >>>>>> Greetings all,
> > >>>>>> In a world where multiple DBSERVERALIAS values exist, is there a way
> > >>>>>> to restrict which ones the Connection Manager tries to establish
> > >>>>>> connections through?
> > >>>>>> As a brief example, If I have these values in the ONCONFIG file:
> > >>>>>> DBSERVERNAME aspbeL1
> > >>>>>> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5> > >>>>>> And given this sqlhosts file:
> > >>>>>> aspbeL1 onipcshm asp5 aspbeL1
> > >>>>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live> > >>>>>> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> > >>>>>> odbc_asp5 onsoctcp asp5 odbc_asp5> > >>>>>> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on
> > >>>>>> the same server.
> > >>>>>> The CM insists on trying to connect via the shared memory service
> > >>>>>> "aspbeL1", which it cannot because the CM is running on a separate
> > >>>>>> server.
> > >>>>>> What I want is for the CM to connect only to service aspbeL1_live. How
> > >>>>>> do I get the CM to ignore those other entries? It even tries to
> > >>>>>> connect to hdr1P_be even though the s=6 setting should (I believe) let
> > >>>>>> the CM know that only HDR-related traffic is allowed on this port.
> > >>>>>> Thanks,
> > >>>>>> Tom
>
> > Hi Tom,
>
> > Well, a few defects to be logged I feel :-/
>
> > 1. dbserveralias=off is not present in 3.50.xC4
>
> > 2. I would suggest that you consider using "group" syntax in your sqlhosts (note shared memory connection is not in the group):
>
> > aspbeL1 onipcshm asp5 aspbeL1> > aspbel group - - i=1
> > aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel
> > hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6
> > odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel
>
> > Really, the "group" should also include the actual HDR secondary, so that if you want to re-direct connections to the HDR secondary
> > you can.
>
> > 3. What INFORMIXSERVER do you start connection manager with?
>
> > I suggest that you use either the "group" aspbel (although this appears to have issues :-/ ) or aspbeL1_live.
>
> > 4. The is an error being generated when one of the Connection Manager tries to use :
>
> > hdr1P_be onsoctcp asp5_be hdr1P_be s=6
>
> > 08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be SQLCODE = (-25539,0,)
>
> > which I think is for your HDR secondary
>
> > > finderr 25539
> > -25539 Invalid connection-type.
>
> > The connection-type is invalid for the database server. This message appears when
> > the database server is configured to address specific connection requests, for examplefor an
> > ER or HDR connection.
>
> > In order for me to (more easily) get a complete picture, can you fill in the blanks :
>
> > Primary :
> > =========
> > DBSERVERNAME aspbeL1
> > DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>
> > Secondary :
> > ===========
> > DBSERVERNAME ??????> > DBSERVERALIAS ??????
>
> > sqlhosts
> > ========
> > # Primary entries
> > aspbeL1 onipcshm asp5 aspbeL1> > aspbel group - - i=1
> > aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel
> > hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6
> > odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel
> > # Secondary entries
> > ??????????
> > hdr1S_be onsoctcp asp6_be hdr1S_be g=aspbel
> > ??????????
> > ??????????
> > ??????????
> > # Connection Manager SLA Entries
> > aspbeL1_live onsoctcp ???????
> > etc. etc.
>
> > Connection Manager INFORMIXSERVER env vars
> > ==========================================
>
> > Connection Manager oncmsm_1 Config File :
> > =========================================
> > NAME oncmsm_1
> > SLA oltp_cm1=aspbeL1_live
> > SLA report_cm1=hdr1_live
> > ????????????
> > LOGFILE (Hopefully separate to oncmsm_2)
>
> > Connection Manager oncmsm_2 Config File :
> > =========================================
> > NAME oncmsm_2
> > SLA ?????????????
> > SLA ?????????????
> > ????????????????
> > LOGFILE (Hopefully separate to oncmsm_1)
>
> > If anything, we can at least get a load of issues logged :-/- Hide quoted text -
>
> > - Show quoted text -
>
> Here is my configuration:
>
> ASP5 is the primary server in an HDR pair. ASP6 is the secondary, or
> HDR server in the pair.
>
> Each server is connected to a private switch that also connects them
> to the application server, which is ASP4. ASP4 is not part of the
> MACH11 Cluster. Each server also connects to a routed switch, that is
> accessible throughout our network. the "_be" in the host name
> indicates "back end", which is the private switch connection.
>
> The goal is to have the CM use ONLY aspbeL1_live and hdr1_live for
> connections. Here is the desired connection usage:
>
> Private switch connections:
>
> aspbeL1_live: Primary. All CM managed connections go here.
> hdr1_live: Secondary. If aspbeL1_live dies - promote to
> active (normally HDR1 is read-only)
>
> hdr1P_be: For HDR server to server traffic only (hence the s=6 value)
> hdr1S_be: For HDR server to server traffic only (hence the s=6 value)
>
> Routed switch connections:
>
> odbc_asp5: To allow non-application server (ASP4) ODBC type
> connections
> munislive: To allow non-application server (ASP4) ODBC type
> connections
>
> Shared Memory connections:
>
> aspbeL1: For internal use only.
> hdr1: For internal use only.
>
> Here are the ASP5 configuration values:
>
> DBSERVERNAME: aspbeL1
> DBSERVERALIASES: hdr1P_be, aspbeL1_live, odbc_asp5
>
> sqlhosts file on ASP5:
> # ASP5
> aspbeL1 onipcshm asp5 aspbeL1> # aspbeL1_live onsoctcp asp5_be aspbeL1_live
> hdr1P_be onsoctcp asp5_be hdr1P_be s=6
> odbc_asp5 onsoctcp asp5 odbc_asp5>
> # ASP6
> # hdr1 onipcshm asp6 hdr1
> # hdr1_live onsoctcp asp6_be hdr1_live
> hdr1S_be onsoctcp asp6_be hdr1S_be s=6
> munislive onsoctcp asp6 munislive>
> # ASP4 Programs connect via this group via the connection manager
> g_mach group - - e=hdr1_live
> aspbeL1_live onsoctcp