Diagnosing Pull Replication Issues

If an update cannot be applied after being pulled by Directory, the update and the error are dumped to the trace log. An update may fail for many reasons, so check the trace log to resolve the issue. A failure may occur when retrieving changes and when applying changes.

Retrieving Changes

If Directory cannot perform a pull search request, the following error is displayed:
ERROR : Pull replication: search of updates from source failed
This error indicates that the source of the updates could not be contacted. Alternatively, the pull search request was rejected for another reason and requires further investigation.

Applying Changes

If an update cannot be applied, the following information is added to the trace log:
ERROR : Pull Replication: update sequence '58' failed. Data integrity may be compromised.
This error is followed by a dump of the failed request and the reason for failure. A request may fail for these reasons:
  • Misconfiguration
  • Unsupported values
  • Directory and ODSEE being out of sync
  • Updates being reapplied
The information from the trace log is a good starting point in tracking down such issues. The warn-log must be monitored for such errors too.

Changes Done by the Replication User on ODSEE Ignored During Pull Replication

Any changes that are done by a replication user on ODSEE are ignored during pull replication to avoid the same change being replicated back to ODSEE. Use a different user to make changes in ODSEE.
For example, you might create
cadir
as a replication user in ODSEE and give it permission to access the change log. You can use this account in the Directory configuration for pull replication. However, if you create new records as
cadir
, these changes do not replicate. You must use a different user to create objects in ODSEE.