Modify Replicate: Advanced Options

Use this page to change the attributes of a replicate, including the conflict resolution rule and scope and the replication frequency.

Conflict Resolution Scope

Specify the scope of Enterprise Replication (ER) conflict resolution. If you change the conflict resolution rule, you must also specify the scope, even if you are not changing the scope.

Table 1. Conflict Resolution Scope
Option	Description
Row	ER evaluates one row at a time. It only applies replicated rows that win the conflict resolution with the target row.
Transaction	(Default) ER applies the entire transaction if the replicated transaction wins the conflict resolution.

Conflict Resolution Rule

Specify the ER conflict resolution rule.

Table 2. Conflict Resolution Rule
Option	Description
Ignore	ER does not attempt to detect or resolve conflicts. A row or transaction either is applied successfully or it fails to replicate. Use the ignore conflict resolution rule if you do not want ER to resolve conflicts. Restriction: When you modify a replicate: You cannot change the conflict resolution rule from ignore to another rule. You cannot change the conflict resolution rule to ignore from another rule.
Always apply	ER does not attempt to detect or resolve conflicts. Replicated changes are applied even if the operations are not the same on the source and target servers. Use the always-apply conflict resolution rule if you do not want ER to resolve conflicts, but you do want replicated changes to be applied even if the operations are not the same on the source and target servers. Attention: Only use the always-apply conflict resolution rule with a primary-target replication system. If you use the always-apply conflict resolution rule with an update-anywhere replication system, your data might become inconsistent.
Stored procedure	ER uses a stored procedure that you provide to determine which data is applied. Type the full name of the procedure in the text box.
Optimize the stored procedure	If this option is selected, ER uses the stored procedure only in these cases: The row to be replicated is from a different database server than the server that last updated the local row on the target table. The row to be replicated has a less recent time stamp than the local row on the target table. In all other cases, ER does not use the stored procedure to resolve the conflict. If this option is not selected, the stored procedure is always used.
Time stamp	(Default) ER evaluates the latest time stamp of the replication against the target and determines how to resolve any conflict. Use the time stamp conflict resolution rule to have the row or transaction with the most recent time stamp take precedence in a conflict. Prerequisite: For this rule to be available, the ER conflict resolution columns (CRCOLS) must be defined in the tables.
Time stamp and stored procedure	ER evaluates the latest time stamp of the replication against the target and determines how to resolve any conflict. If the time stamps are identical, ER uses a stored procedure that you provide to resolve the conflict. Type the full name of the procedure in the text box. Prerequisite: For this rule to be available, the ER conflict resolution columns (CRCOLS) must be defined in the tables.
Delete wins	Delete and insert operations always win over update operations. All other conflicts are resolved by comparing time stamps. Use the delete wins conflict resolution rule to have the row or transaction with a delete operation take precedence in a conflict and to resolve all other conflicts by comparing time stamps. The delete wins conflict resolution rule prevents upserts. Prerequisite: For this rule to be available, the ER conflict resolution columns (CRCOLS) must be defined in the tables.

Floating Point Format

Specifies how ER transfers replicated floating-point numbers. You cannot change the floating point format.

Table 3. Floating Point Format
Option	Description
IEEE	(Default) ER transfers replicated floating-point numbers in either 32-bit (for SMALLFLOAT) or 64-bit (for FLOAT) IEEE floating-point format. Use this option for all new replicate definitions.
Canonical	ER transfers replicated floating-point numbers in machine-independent decimal representation. This format is provided for compatibility with earlier versions only.

Special Options

Specify any of these special options.

Table 4. Special Options
Option	Description
Activate aborted transaction spooling (ATS)	Activates aborted transaction spooling for replicate transactions that fail to be applied to the target database, if the conflict resolution rule is other than ignore or always-apply. By default, ATS is not activated.
Activate row information spooling (RIS)	Activates row-information spooling for replicate row data that fails conflict resolution or encounters replication order problems, if the conflict resolution rule is other than ignore or always-apply. By default, RIS is not activated.
Replicate full row	Specifies to replicate the full row and enable upserts. If this option is not selected, ER replicates only changed columns and disables upserts. By default, ER always replicates the entire row and enables upserts.
Fire triggers at destination	Specifies that the rows that are inserted by this replicate fire triggers at the destination. By default, triggers are not fired at the destination table.
Retain deleted rows	Specifies that rows are retained if they are deleted on other nodes in the ER system. By default, deleted rows are not retained.
Enable replication between code sets (UTF-8)	Specifies that character columns are converted to UTF-8 when the row is copied into the transmission queue. When the replicated row is applied on the target server, the data is converted from UTF-8 to the code set that is used on the target server. No attempt is made to convert character data contained within opaque data types such as user-defined types (UDTs) or DataBlade data. Prerequisite: This option requires IBM® Informix® 11.70.xC3 or later.

Frequency

Specify the interval between replications or when the replication should occur.

Table 5. Frequency
Option	Description
Immediately	(Default) Replication occurs immediately when data arrives.
Repeat every	Replication occurs when the replicate set is defined and then regularly at the interval that you specify in hours and minutes. For example, if you select this option and 5 Hours and 45 Minutes, the replication occurs immediately and then every 5 hours and 45 minutes.
At this day and time	Replication occurs at the day and time that you specify. For example, if you specify Daily at 17 Hours and 45 Minutes, replication occurs every day at 5:45 p.m. If you specify Weekly on Sunday at 17 Hours and 45 Minutes, replication occurs every Sunday at 5:45 p.m.