Help needed: sqlhosts basics

Hi all. We try to configure an IDS 9.21 FC2 on Solaris 7 with HDR. The clients though are 32-bits, so we were told to use TCP connections, not shared memory. For the previous version used (7.30), we were using shared memory, and our sqlhosts on one of the servers looks like: inf_shm onipcshm server_1 some_name inf_tlia ontlitcp server_1 infserv_sys otherinf_tlia ontlitcp server_1 otherserv_sys inf_tlib ontlitcp server_2 infserv_sys otherinf_tlib ontlitcp server_2 otherserv_sys My questions are: 1. How does HDR know which connection to use for HDR if there are more entries in the sqlhosts for the secondary server ? 2. Do we need to replace the shared memory connection with a new TCP one, listening to a new port, or we can use the existing TCP connection ? 3. Are there any performance issues if we use the same TCP connection ? Thanks in advance, Bogdan Neagu

Bogdan Neagu wrote: > > Hi all. > > We try to configure an IDS 9.21 FC2 on Solaris 7 with HDR. The clients > though are 32-bits, so we were told to use TCP connections, not shared > memory. > > For the previous version used (7.30), we were using shared memory, and > our sqlhosts on one of the servers looks like: > > inf_shm onipcshm server_1 some_name > inf_tlia ontlitcp server_1 infserv_sys > otherinf_tlia ontlitcp server_1 otherserv_sys > inf_tlib ontlitcp server_2 infserv_sys > otherinf_tlib ontlitcp server_2 otherserv_sys> > My questions are: > 1. How does HDR know which connection to use for HDR if there are more > entries in the sqlhosts for the secondary server ? When you define the replicant you specify the servername to use that corresponds to a network connection. Anyway you should not have any shared memory entries for remote servers in the local sqlhosts file the only one(s) should be for the local server(s). BTW to prevent confusion and ease script and program migration I alias connections and use a primary/secondary naming scheme rather than share_memory/network. Thus on host_1 I have: svr_1 onipcshm host_1_lv0 service_0 svr_1_e ontlitcp host_1_lv0 service_1 svr_1_f ontlitcp host_1_fddi service_2 svr_2 ontlitcp host_2_lv0 service_1 svr_2_e ontlitcp host_2_lv0 service_1 svr_2_f ontlitcp host_2_fddi service_2 While in the sqlhosts file in svr_2 I have: svr_1 ontlitcp host_1_lv0 service_1 svr_1_e ontlitcp host_1_lv0 service_1 svr_1_f ontlitcp host_1_fddi service_2 svr_2 onipcshm host_2_lv0 service_0 svr_2_e ontlitcp host_2_lv0 service_1 svr_2_f ontlitcp host_2_fddi service_2 Note the aliasing. In this way I almost always refer to the server on host_1 as svr_1 and the server on host_2 as svr_2 regardless of whether I am running the client on host_1, host_2, or some other machine. > 2. Do we need to replace the shared memory connection with a new TCP > one, listening to a new port, or we can use the existing TCP connection > ? You can use an existing one. > 3. Are there any performance issues if we use the same TCP connection ? No. Art S. Kagel