Connecntion Manager x DBSERVERALIASES
Posted in 2010
Hi, csdk 3.50 xC7 ifx 11.50 xF7 - Linux. I got a issue here to configure the Connection Manager over a HDR cluster and theirs DBSERVERALIASES. On the configuration of the two instances, exists some aliases what not should be considered to client connectivity. I already notice that configurations of the listeners network what the client isn't capable to use, they ignore and not try o redirect the client to them (differ networks/netmask). But I want to get more control over the serveralias/services what a SLA will redirect. For example, If I configure a serveralias/service specific for ER , what work on the same network of the clients, but is a different port, I don have how avoid the CM to redirect a connection to this service/port. If for some reason later I want to do some maintenance on this service and put down this listener I will kill users sessions... I don't found anything on the manuals. I already try force the servername on the SLA configuration, don't work... the CM detect the others listeners and redirect to them. I try create a specific sqlhosts for the CM, without the serveralias/services what I don't want they redirect... this is worst, the CM don't start this way, they need to "see" all serveralias.... I don't want to set the s=6 for this situation because I already have a lot of problems with this parameters (the $INFORMIXDIR/etc/hosts.equiv appear not work well). And this is not the unique situation, I have listeners/port specific for admin connectivity what not should be considered to cluster/SLAs redirects. So, there is some way to do this what I missing here?