cdr autoconfig serv
The cdr autoconfig serv command can autoconfigure connectivity for servers in a high-availability cluster or Enterprise Replication domain, and can automatically configure replication.
Syntax
Element | Purpose | Restrictions |
---|---|---|
host | The name of a database server host. | |
port | The port number that is used for communication |
The following table describes the options to cdr autoconfig serv.
Long Form | Short Form | Meaning |
---|---|---|
--sourcehost | -H | The host of the database server that is sending autoconfiguration information. If --sourcehost and --sourceport are not specified, the database server where the command is run is considered the source database server. |
--sourceport | -P | The port that is used by the database server that is sending autoconfiguration information. |
--targethost | -h | The host of the database server that is receiving autoconfiguration information. |
--targetport | -p | The port that is used by the database server that is receiving autoconfiguration information. |
Usage
Run the cdr autoconfig serv command
to autoconfigure connectivity for servers in a high-availability cluster
or Enterprise Replication domain, and to autoconfigure replication
if you are adding database servers to an Enterprise Replication domain.
The CDR_AUTO_DISCOVER configuration parameter must be set to 1
on
all database servers that are participating in an Enterprise Replication
domain or high-availability cluster, before you can run the cdr
autoconfig serv command. A newly installed database severs
that is added to an Enterprise Replication domain through the cdr
autoconfig serv command must have a configured storage pool.
- The source server propagates its trusted-host file to target server.
- The target server adds entries for itself and all other replication servers to its sqlhosts file.
- The source server updates its sqlhost file with entries for the target server.
- Each replication server updates its sqlhost file and trusted-host file with entries for the target server.
- The target server sets its CDR_DBSPACE configuration parameter and creates the dbspace that is required for Enterprise Replication.
- The target server sets its CDR_QDATA_SBSPACE configuration parameter and creates the sbspace that is required for Enterprise Replication.
- The aborted transactions spooling (ATS) file directory $INFORMIXDIR/tmp/ats_dbservername is created on the target server.
- The row information spooling (RIS) file directory $INFORMIXDIR/tmp/ris_dbservername is created on the target server.
- Replication of the domain information in the syscdr catalog to the target server starts.
- The source server adds entries for itself to its sqlhosts file.
- The source server sets its CDR_DBSPACE configuration parameter and creates the dbspace that is required for Enterprise Replication.
- The source server sets its CDR_QDATA_SBSPACE configuration parameter and creates the sbspace that is required for Enterprise Replication.
- The aborted transactions spooling (ATS) file directory $INFORMIXDIR/tmp/ats_dbservername is created on the source server.
- The row information spooling (RIS) file directory $INFORMIXDIR/tmp/ris_dbservername is created on the source server.
- All replication servers must be active, or the cdr autoconfig serv command fails.
- Do not run the cdr autoconfig serv command if you have configured trusted-host information, manually, rather than through running the admin() or task() function with the cdr add trustedhost argument.
- Do not run the cdr autoconfig serv command if your replication servers have secure ports configured.
- The cdr autoconfig serv command does not copy hosts.equiv information to the trusted-host file that is set by the REMOTE_SERVER_CFG configuration parameter. Run the admin() or task() function with the cdr add trustedhost argument if you must add information from the hosts.equiv file to the trusted-host file that is set by the REMOTE_SERVER_CFG configuration parameter.
Database servers are configured serially. Parallel configuration is not supported.
You can run this command from within an SQL statement by using the SQL administration API.
Example 1: Define Enterprise Replication on a database server
- server_1 on host_1
cdr autoconfig serv
The command defines Enterprise Replication on server_1.
Example 2: Configure connectivity and ER between two stand-alone servers by using source syntax
- server_1 on host_1
- server_2 on host_2
cdr autoconfig serv -c server_2 --sourcehost host_1 --sourceport 9000
- The command connects to server_2.
- Enterprise Replication is defined on server_1.
- Enterprise Replication is defined on server_2.
- server_1 replicates the domain data to server_2.
Example 3: Configure connectivity and ER between two stand-alone servers using target syntax
- server_1 on host_1
- server_2 on host_2
cdr autoconfig serv -c server_1 --targethost host_2 -targetport 9002
- The command connects to server_1.
- Enterprise Replication is defined on server_1.
- Enterprise Replication is defined on server_2.
- server_1 replicates the domain data to server_2.
Example 4: Configure connectivity and ER between two stand-alone servers
- server_1 on host_1
- server_2 on host_2
- server_3 on host_3
cdr autoconfig serv --targethost hos_t2 -targetport 9002
cdr autoconfig serv --targethost host_3 -targetport 9003
- The first command connects to server_1.
- Enterprise Replication is defined on server_1.
- Enterprise Replication is defined on server_2.
- server_1 replicates its data to server_2.
- The second command connects to server_1.
- Enterprise Replication is defined on server_3.
- server_1 replicates the domain data to server_3.