More Connection Manager fun

IDS 11.5FC6 on Centos 5.4 I've set up 2 Connection Managers and a 2-node SDS cluster. When I get to run dbaccess on the client I get to see ALL possible connections; ie the path to the relevant IDS instance twice, once for each Connection Manager in the Connection Manager cluster: # INFORMIXSERVER=ids_report ; dbaccess sysadmin@ids_report1 sysuser@ids_report2 sysha@ids_report1 sysutils@ids_report2 sysmaster@ids_report1 sysuser@ids_report1 sysutils@ids_report1 stores_demo@ids_report2 sysadmin@ids_report2 sysha@ids_report2 Is this to be expected? It doesn't matter, if I just type # dbaccess stores_demo I get straight in via one or the other Configuration Managers; onstat -g cmsm on the database shows me it alternates between the two, which is what the c=1 does I think. I'm just interested to understand it beter. Client sqlhosts: ids_oltp group - - i=10,c=1 ids_oltp1 onsoctcp cm1_internal 9051 g=ids_oltp ids_oltp2 onsoctcp cm2_internal 9051 g=ids_oltp ids_report group - - i=10,c=1 ids_report1 onsoctcp cm1_internal 9052 g=ids_report ids_report2 onsoctcp cm2_internal 9052 g=ids_report Thanks

informix-list-bounces@iiug.org wrote on 05/30/2010 06:12:56 AM: > From: "Neil Truby" <neil.truby@ardenta.com> > To: informix-list@iiug.org > Date: 05/30/2010 06:15 AM > Subject: More Connection Manager fun > Sent by: informix-list-bounces@iiug.org > > IDS 11.5FC6 on Centos 5.4 > > I've set up 2 Connection Managers and a 2-node SDS cluster. When I get to > run dbaccess on the client I get to see ALL possible connections; ie the > path to the relevant IDS instance twice, once for each Connection Manager in > the Connection Manager cluster: > > # INFORMIXSERVER=ids_report ; dbaccess > > sysadmin@ids_report1 sysuser@ids_report2 > sysha@ids_report1 sysutils@ids_report2 > sysmaster@ids_report1 > sysuser@ids_report1 > sysutils@ids_report1 > stores_demo@ids_report2 > sysadmin@ids_report2 > sysha@ids_report2 > > Is this to be expected? It doesn't matter, if I just type It is expected. This has nothing to do with connection manager, this is how dbaccess works. When you run dbaccess (without a database name), dbaccess connects to a instance (defined by INFORMIXSERVER) and get the database list for you. In your case, you have set INFORMIXSERVER to a server group (ids_report) that prompted dbaccess to connect to all the instances in that server group and get the database list for you. > > # dbaccess stores_demo> > I get straight in via one or the other Configuration Managers; onstat -g > cmsm on the database shows me it alternates between the two, which is what > the c=1 does I think. I'm just interested to understand it beter. By default (c=0), connection to a server group will always select a instance from the group in the order they are listed. Group option c=1 let you select a server randomly from the server group. You have only two servers defined in the group, hence it look like it alternates between the two. - Nilesh - > > Client sqlhosts: > ids_oltp group - - i=10,c=1 > ids_oltp1 onsoctcp cm1_internal 9051 g=ids_oltp > ids_oltp2 onsoctcp cm2_internal 9051 g=ids_oltp > > ids_report group - - i=10,c=1 > ids_report1 onsoctcp cm1_internal 9052 g=ids_report > ids_report2 onsoctcp cm2_internal 9052 g=ids_report > > Thanks > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list