Replication error log extended operation

Edit online

The replication error log extended operation explains its use with the server and provides the results.

Description
Use this extended operation to monitor replication errors and correct any problems that occur as data fails to be replicated.
Note: This extended operation is always enabled.
Request
OID
1.3.18.0.2.12.56
Syntax
The value consists of an integer which indicates the type of request and two strings in BER format. The first string identifies which failure or failures are to be deleted, attempted again or displayed. The value is either 0 for all, or the ID of the failed change. The second string provides the DN for the replication agreement.
Response
OID
1.3.18.0.2.12.57
Syntax
The response is a string that indicates any problem that occurred, or if successful, how many failed changes were deleted or present to the consumer.
Behavior
The extended operation acts on the table that maintains the updates that failed on any of the current server consumer servers. The data for any single failure can be displayed. Any or all failed changes can be deleted or attempted again. Deleted changes are removed from the table. Changes that attempted again are sent individually to the consumer. If the update succeeds, the failure is removed from the table. If the update fails again, it is added back as a new failure with the following results to reflect this update:
  • number of attempts
  • last time that attempted
  • result code that is updated
The original failure is removed. The worker thread that handles the extended operation connects to the consumer and sends these changes. Replica threads can send updates to the consumer at the same time.
The following persons are enabled to call the extended operation:
  • Primary Directory Administrator
  • Local Administration Group member
  • Users with write access to the replica group
Note: If the extended operation is called by a user who does not have access, LDAP_INSUFFICIENT_ACCESS is returned.
This extended operation has the following possible return codes:
  • LDAP_SUCCESS
  • LDAP_INSUFFICIENT_ACCESS
  • LDAP_DECODING_ERROR
  • LDAP_PROTOCOL_ERROR
  • LDAP_UNWILLING_TO_PERFORM
  • LDAP_NO_SUCH_OBJECT
This extended operation is not supported by the Administration Server.
Scope
If the errors are deleted or successfully attempted again, they are removed from the table permanently.
Auditing
The additional information in the audit log is consists of three lines: 
Replication Error Log Management Option: [ SHOW | RETRY | DELETE | UNKNOWN ]
Replication Error ID: numeric value 
Replication Agreement DN: DN or empty string.