OUD to ODSEE Replication Failing Through Replication Gateway if the ODSEE Replica Previously had a Different Replica ID (Doc ID 2909292.1)

Last updated on DECEMBER 01, 2022

Applies to:

Symptoms

Replication from OUD to ODSEE using Replication Gateway is not working, however it does work in the opposite direction (ie; ODSEE to OUD)

Attempting to remove the OUD instance and replication gateway, and then reinitializing the replica back does not resolve the issue.

The only error in the replication gateway log when debug is enabled may be like this:

---
[TIMESTAMP] 8 message error thread={Replication Listener for server id <SERVER ID> and domain <DOMAIN>)} threadDetail={parentThread=Worker Thread <THREAD_NUMBER> isDaemon=false } method={processUpdate(GatewayDomain.java:1240)} Add change cn: <CN> to the opends pending queue
Stack Trace:
  java.lang.Thread.getStackTrace(Thread.java:1559)
  org.opends.server.loggers.debug.DebugTracer.debugMessage(DebugTracer.java:739)
  org.opends.server.loggers.debug.DebugTracer.debugError(DebugTracer.java:689)
  com.sun.gateway.server.GatewayDomain.processUpdate(GatewayDomain.java:1240)
  org.opends.server.replication.service.ListenerThread.run(ListenerThread.java:102)
---

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.