My Oracle Support Banner

OUD 11g - DIP Import Synchronization Stops if Change to be Replayed from ODSEE Contains Base64 Encoded Value for TargetDN (Doc ID 2397957.1)

Last updated on AUGUST 25, 2020

Applies to:

Oracle Unified Directory - Version and later
Oracle Internet Directory - Version 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, for this intermittent issue, after some 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.


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

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