OUD11g - Replication Purge History Command Does Not Complete and Errors with "LDAP response read timed out"
(Doc ID 2511279.1)
Last updated on DECEMBER 14, 2022
Applies to:
Oracle Unified Directory - Version 11.1.2.3.170418 and laterInformation in this document applies to any platform.
Symptoms
Running 'dsreplication purge-historical' command on a daily basis, the command occasionally shows a time out and then unable to successfully complete the purge.
# $OUD_Instance/bin/dsreplication --adminUID ADMIN --adminPasswordFile $OUD_Instance/config/PWD_FILE purge-historical --maximumDuration 3600 --readTimeout 3600000 --baseDN o=SUFFIX -X -n'
Establishing connections and reading configuration ..... Done.
Purging historical on base DNs:
o=SUFFIX
[15/Nov/2017:21:05:39 -0500] severity="NOTICE" msgCount=0 msgID=9896349 message="Purge historical task Purge historical on server <HOST>:<PORT>for base DNs: o=SUFFIX started execution"
An error occurred polling the task launched on server:
<HOST>:<PORT>. Details: LDAP response read timed out, timeout used:30000ms.
See /tmp/oud-replication-123456xxxx.log for a detailed log of this operation.
Tried to specify '--readTimeout 3600000' to match '--maximumDuration 3600', does not work, then readTimeout is ignored as the default value of 30000ms is referenced in the time out error message.
When the time out occurs, a subsequent attempt to run 'dsreplication status' fails with times out too
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 |
| Cause |
| Solution |
| References |