Intermittent User Rename Operation Failure Due To Multiple LDAP Hosts Added For HA
(Doc ID 1968734.1)
Last updated on APRIL 03, 2017
Applies to:Identity Manager - Version 220.127.116.11.0 and later
Oracle Unified Directory - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Observing intermittent issues due to adding multiple ldap hosts for HA to LDAPSync configuration using following wlst command:
addLDAPHost(adapterName='ldap1', host='myhost.example.domain.com', port=389, contextName='myContext')
User Rename operations intermittently return orchestration process failed error. Post this if we try to search OIM, we find the user with old user id. If we search the user in LDAP, we are not able to find the old user in LDAP but the new user is available with the same orclguid.
On looking at the OUD logs, the access logs show that OIM performed mod rdn operation on one of the OUD instance which succeeded. Then OIM invokes the search operation for the modified user and if this operation lands on a different OUD server before the replication has taken place, it fails and the orchecstration process fails, leaving the OUD user in the modified state with new UID while the OIM user still has the old UID.
Is there a way to configure failover for OUD server or some configurations in OIM so that for one orchestration process, it does not use different connections?
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