My Oracle Support Banner

OUD 11g/12c - Replication Server Disconnects Causing Replication Failures and TimeThread Errors With High CPU / High Memory (Doc ID 2652409.1)

Last updated on MARCH 30, 2020

Applies to:

Oracle Unified Directory - Version 12.2.1.3.190522 and later
Information in this document applies to any platform.

Symptoms

Replication showing connection issue -

<SUFFIX_DN> - Replication Enabled
===========================

Server : Entries : M.C. [1] : A.O.M.C. [2] : Port [3] : Status [4] : Conflicts [5]
-----------------------------:----------:----------:--------------:----------:----------------:--------------
...
<HOSTNAME1>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Not Connected : 8
<HOSTNAME2>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Not Connected : 8
<HOSTNAME3>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Not Connected : 8
<HOSTNAME4>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Normal : 8
<HOSTNAME5>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Normal : 8
<HOSTNAME6>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Not Connected : 8
<HOSTNAME7>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Normal : 8
<HOSTNAME8>:<ADMIN_PORT> : 7806337 : 0 : 0 : -- [7] : Not Connected : 8

In the OUD errors log -

- TimeThread errors -

category=CORE severity=MILD_WARNING msgID=xxxxx msg=The TimeThread is late (xxxxx ms)

- Replication Server (RS) Errors -

severity=SEVERE_ERROR msgID=14942327 msg=Caught Exception during initial communication (phase 1) on domain <SUFFIX_DN> with replication server <FQDN>:<REPL_PORT> : Connection reset

category=SYNC severity=NOTICE msgID=xxxxx msg=Could not connect to any replication server on suffix <SUFFIX_DN> among the following RS candidates...

category=SYNC severity=SEVERE_ERROR msgID=xxxxx msg=The connection to replication server <FQDN>/<IP>:<REPL_PORT> xxx has been unexpectedly dropped by the replication server for <SUFFIX_DN> in local server id xxxxx

category=SYNC severity=SEVERE_ERROR msgID=xxxxx msg=Caught Exception during initial communication (phase 1) on domain <SUFFIX_DN> with replication server <FQDN>:<REPL_PORT> : Read timed out...

category=SYNC severity=SEVERE_ERROR msgID=xxxxx msg=Caught Exception during initial communication (phase 1) on domain cn=admin data with replication server <FQDN>:<REPL_PORT> : connect timed out...

 

Changes

Deleted millions of entries

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


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