WebLogic Portal (WLP) LDAP and Database Out of Sync
(Doc ID 1061447.1)
Last updated on APRIL 23, 2021
Applies to:Oracle WebLogic Portal - Version 8.1 and later
Information in this document applies to any platform.
There are times when WebLogic Portal's (WLP) Embedded LDAP (LDAP) and Database (DB) become "out of sync" and corrupted. When the LDAP and DB do become out of sync it is difficult to determine the extent of the corruption.
The process of recovering from this corruption can be extremely tedious, time consuming and usually causes a loss of data. The data loss can include Users and Groups, Entitlements and Delegated Administration stored in the Embedded LDAP.
This corruption has been known to happen in all WLP versions from 8.1 through to 10.3.
See the last section in this document on migrating to the RDBMS Security Store in 10.3.2.
The purpose of this document is to help diagnose, troubleshoot and resolve issues related to the WLP LDAP and DB going out of sync.
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
|What is the cause of the corruption and how does the LDAP become out of sync with the DB?|
How do you know when the LDAP and DB are out of sync?
|Recovering from the corruption|
|What to do if the PortalSystemDelegator Role is corrupt (missing)|
|Migration to the RDBMS Security Store when LDAP / DB is out of sync due to missing policies in LDAP (This option is only applicable for 10.3.2 and later versions)|