Creates a logical connection. Replication Server uses logical connections to manage warm standby applications.
create logical connection to <data_server>.<database> [set <logical_database_param> [to] ‘<value>’ [set <logical_database_param> [to] ‘<value>’]...]
The name of a data server. The data server does not have to be a real data server.
The name of a database. The database does not have to be a real database.
The name of the configuration parameter that affects logical connections. Configuration parameters affecting logical connections describes the parameters that you can set with create logical connection.
Creates a logical connection called <LDS.logical_pubs2>:
create logical connection to LDS.logical_pubs2
Creates a logical connection for an existing connection. For example, you would enter this if the database <TOKYO_DS.pubs2> already exists and will serve as the active database in the warm standby application:
create logical connection to TOKYO_DS.pubs2
create logical connection creates a logical connection to be used with warm standby applications. See the Replication Server Administration Guide Volume 2 for information about setting up and managing warm standby applications.
The logical connection is for a symbolic <data_server>.<database> specification. The data server and database do not have to be real; Replication Server maps them to the current active database.
If you are creating a logical connection for an existing connection, <data_server>.<database> must refer to the data server and database names of the existing connection. Otherwise, it is recommended that the logical name be different from the active and standby database names.
Replication definitions and subscriptions use the logical connection name.
After you create the logical connection, use rs_init to add the physical active and standby databases for the logical connection.
create logical connection requires “sa” permission.