Creating sqlhost group entries for replication servers

The sqlhosts file on the host of each replication server must specify a group entry for each replication server in an Enterprise Replication domain. You can manually specify sqlhost file information, or run the cdr autoconfig serv command to add entries to a database server's sqlhost file, and then propagate the entries to other database servers in an Enterprise Replication domain. However, if you are configuring secure ports, you cannot use the cdr autoconfig serv command.

Typically, a server group includes only one database server. However, if the computer has multiple network protocols or network interface cards, the server group includes all aliases for the database server. Enterprise Replication treats the server group as one object, whether it includes one or several database server names.
The following example shows sqlhosts file entries for four Enterprise Replication servers:
  • serv1
  • serv2
  • serv3
  • serv4
#dbservername  nettype   hostname             servicename  options
 g_serv1       group     -                    -            i=143
 serv1         ontlitcp  ny.usa.com           1230         g=g_serv1
 
 g_serv2       group     -                    -            i=144
 serv2         ontlitcp  tokyo.japan.com      1231         g=g_serv2
 
 g_serv3       group     -                    -            i=145
 serv3         ontlitcp  rome.italy.com       1232         g=g_serv3
 
 g_serv4       group     -                    -            i=146
 serv4         ontlitcp  perth.australia.com  1233         g=g_serv4
Each server has two entries of information:
  • A group definition, which specifies a group name and unique ID for the replication server
  • Connectivity information for the database server

All Enterprise Replication commands and options use the name of the database server group or the more familiar database server name (that is, the name that is specified by the INFORMIXSERVER environment variable) for all references to database servers. The exception is the --connect option, which can use either a server name or a group name.

Leaf servers in hierarchical routing topologies do not require connectivity information for all replication servers. A leaf server requires connectivity information for only itself and its parent.


Copyright© 2019 HCL Technologies Limited