Ignore Conflict-Resolution Rule

The ignore conflict-resolution rule does not attempt to detect or resolve conflicts.

A row or transaction either applies successfully or it fails. A row might fail to replicate because of standard database reasons, such as a deadlock situation, when an application locks rows. Use the ignore conflict-resolution rule only with a primary-target replication system. If you use ignore with an update-anywhere replication system, your data might become inconsistent.

The ignore conflict-resolution rule can be used only as a primary conflict- resolution rule and can have either a transaction or a row scope (as described in Conflict Resolution Scope).

The following table describes how the ignore conflict resolution rule handles INSERT, UPDATE, and DELETE operations.

Table 1. Ignore Conflict-Resolution Rule
Row Exists in Target? INSERT UPDATE DELETE
No Apply row Discard row Discard row
Yes Discard row Apply row Apply row
When a replication message fails to apply to a target, you can spool the information to one or both of the following directories:
  • Aborted-transaction spooling (ATS)

    If selected, all buffers in a failed replication message that compose a transaction are written to this directory.

  • Row-information spooling (RIS)

    If selected, the replication message for a row that cannot be applied to a target is written to this directory.

For more information, see Failed Transaction (ATS and RIS) Files.