You can configure missing replication changes to prevent server lockdowns that are
caused by missing changes. The configuration uses the
missing-changes-policy
enumeration configuration property.
Configuring missing replication changes makes it easier to:
- Recover from difficult cases of missing changes lockdowns.
- Configure replication to favor up-time at the expense of data integrity. Missing changes will optionally be ignored and replication will continue.
Note:
There can only be one instance of missing-changes-policy
per
replication server and one instance per replication domain on each replication
server.