OUD 11g - DIP Import Synchronization Stops if Change to be Replayed from ODSEE Contains Base64 Encoded Value for TargetDN
Last updated on MAY 17, 2018
Applies to:Oracle Unified Directory - Version 126.96.36.199.180116 and later
Oracle Internet Directory - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Bi-directional synchronization has been successfully configured where OUD is the DIP backend source directory server and ODSEE is the connected directory. Export profile (OUD to ODSEE) and import profile (ODSEE to OUD) have been successfully associated to each other. DIP synchronization works successfully in both directions.
However, after a random amount of time has passed, the import profile (ODSEE to OUD) stops working and efforts to restart synchronization by restarting WLS and all DIP related services does not help. The export profile continues to successfully synchronize data from OUD to ODSEE when the import profile has stopped synchronizing from ODSEE to OUD.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms