Replication error table
You can know more about replication error table using the information provided here.
The replication error table logs failing updates for later recovery. When replication starts, the number of failures logged for each replication agreement is counted. This count is incremented if an update results in a failure, and a new entry is added into the table.
- The replication agreement ID.
- The replication change ID.
- The timestamp for when the update was attempted.
- The number of attempts made (this values is 1 by default, and increments for each attempt made).
- The result code from the consumer.
- All of the information from the replication operation pertaining to the update, for example, the DN, the actual data, controls, flags, and so forth.
If the value specified by the attribute ibm-slapdReplMaxErrors in the server configuration is 0, replication continues processing updates. The attribute ibm-slapdReplMaxErrors is an attribute in the replication configuration entry and it can be changed dynamically.
- Single threaded
- Replication goes into a loop trying to replicate the failing update.
- Multi-threaded
- Replication is suspended.
If the server is configured to use a single connection, replication attempts to send the same update after waiting for 60 seconds and keeps trying until replication succeeds or the administrator skips the update.
For a server configured to use multiple connections, replication is suspended for this agreement. The receiver threads continue polling for status from any updates that have been sent, but no more updates are replicated. To resume replication, the directory administrator must clear at least one error for this agreement or increase the limit with a dynamic modification of the server configuration.
For more information, see "Replication error log extended operation" in Programming Reference.