Defining a replicate

Define the replication participants and replication attributes including how frequently to replicate the data and how to handle conflicts.

With the Define Replicate action, you define a strict master replicate and its participants. A master replicate verifies that replicated tables on different servers have consistent column data types. A strict master replicate also verifies that the replicated tables have identical column names. All database servers containing master replicates must be able to establish a direct connection with the master replicate database server.

Prerequisite: A table must have a primary key to be a replication participant. In addition, the table must be an actual table. It cannot be a synonym, a view, or a sequence. Also, it cannot be an external table. Only tables that can be replication participants appear in the list of selectable tables.

To define a replicate and the replication participants:

On the menu of the HCL OpenAdmin Tool (OAT) for Informix®, expand Replication, and then click Replicates.
Click the Replicates tab.
On the Actions menu, click Define Replicate.
Type a unique name for the replicate.
Select the server group to use as the basis of the master replicate from the Master Replicate Server list.
To automatically create tables on the target server that exist on the master replicate server but not on the target server, select Create missing tables on target servers.
Select the tables and replication servers that you want to define as participants in the replicate by using the filters.
1. For Database filter, type all or part of the database name.
2. For Table filter, type all or part of the table name. Continue filtering the list until a single participant is displayed for each server.
3. To select all the participants specified by the filters, click Select.
  You can also select or clear a table by clicking it in the list.
Note: The master replicate server must be a participant in the new replicate. When you select the tables to participate in the replicate, you must select a table on the master replicate server.
Specify the participant type: primary or receive-only. The default is primary: the participant both sends and receives data. To change the option, click the icon.
Specify which privileges are used to apply the replicated data. The default is table owner. To change the option, click the icon.
To set the advanced options for the replicate, click Next, or to create the replicate with the default values for the advanced options, click Finish.
ER verifies that the tables on the different servers have consistent column data types and identical column names. If Next and Finish are not available, the tables are not consistent.
Optional: Specify the advanced options:
- Conflict Resolution Scope. The default is transaction.
- Conflict Resolution Rule. The default is time stamp.
- Floating Point Format. The default is IEEE.
- Activate aborted transaction spooling (ATS). By default, ATS is not enabled.
- Activate row information spooling (RIS). By default, RIS is not enabled.
- Replicate full row. By default, full rows are replicated. This option is enabled.
- Fire triggers at destination. By default, triggers are not fired at the destination table.
- Retain deleted rows. By default, deleted rows are not retained.
- Frequency of replication. The default is immediately when data arrives.
To create the replicate, click Finish.