You can use OUD for completing the following.<\/em><\/p>\n Pre Step<\/em><\/p>\n You need to enable External change log as a pre-step to proceed with migration. The External Change log (ECL) is available by default on any server instance that includes both Directory server and Replication server. The ECL is enabled when directory server is configured as part of replication topology during installation, or you can configure replication by running dereplication command.<\/p>\n Verify change log is enabled, by running below command.<\/p>\n DIP and OID are configured and deployed<\/em><\/p>\n DIP-OID synchronization is possible with SSL mode only, you need to create OID wallet to allow the bind to OID in SSL mode. A self-signed wallet is needed to create using Enterprise manager and that should be copied to the Oracle wallet using the following steps.<\/p>\n Steps to create OID Self signed Certificate:<\/p>\n Export Trusted certificate and copy it to Oracle Wallet manager.<\/p>\n Create OID Wallet from OWM and copy trusted certificate to wallet<\/p>\n Bind to OID1 in SSL mode using below command.<\/em><\/p>\n Create keystore using Keytool with OID self-signed certificate<\/em><\/p>\n Enter keystore password:<\/p>\n Re-enter new password:<\/p>\n <\/p>\n Update DIP Config to point keystore location<\/em><\/p>\n Configure DIP in SSL V2 mode using below command.<\/em><\/p>\n Update Java Key store using wlst.sh and restart OID and DIP services to effect this changes.<\/em><\/p>\n You need to create Suffix_dn entry in OID to populate OUD data. It is very important to choose which suffix to create and it will be directly used during synchronization profile management. Select parent directory as shown in the following screenshot.<\/p>\n Go to Menu > select OID in Identity and Access > OID Administration and select Synchronization profile as shown in the following image.<\/p>\n Create as below 2 Synchronization profiles.<\/p>\n OUD > OID: OUDImport<\/em> OID > OUD: OUDExport<\/em><\/p>\n You need to decide whether OID should be used as a source or destination while creating synchronization profile.<\/p>\n Use host name and port as OID hostname and port number as OID is being used as a source. Once above mapping is complete, OUDImport \/OUDExport maps Once mapping is enabled, by default the following attributes get automatically mapped.<\/p>\n Add OID ACI to allow DIP to access the suffix DN, inorder to perform syncProfileBootstrap.<\/p>\n Add OID ACI using the following commands.<\/p>\n Run ldapmodify command to add ACI.<\/p>\n Run the following command to bootstrap data from OID to OUD.<\/p>\n The bootstrap operation completed, the operation results are:<\/em><\/p>\n Now you will be able to see suffix data at OUD side.<\/p>\n The Schemasync utility enables to synchronize schema attributes and object classes between OID and other the third party LDAP Directory.<\/p>\n <\/p>\n Once the above command is executed, verify DN details in the Destination directory server.<\/p>\n The methods show in this post to migrate existing OID store to OUD to support large applications to enable single sign-on solutions. OUD provides high performance in users authentication process as LDAP server stores date. Migration steps are very straightforward to implement in any type of applications.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Oracle Internet Directory Migration to Oracle Unified Directory<\/p>\n","protected":false},"author":2,"featured_media":6989,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","format":"standard","meta":{"content-type":"","nid":"26042","content_type":"blog","created_by":"11255","authored_on":"2023-09-14T21:27:58+00:00","field_article_industries":"","tag_category":"Technical","field_blog_author_text":"by Rackspace Technology Staff","seo_description":"Learn about migrating from Oracle Internet Directory (OID) to Oracle Unified Directory (OUD). Understand features and synchronization approaches.","field_featured_image":"","insights_image":"\/wp-content\/uploads\/2026\/blog_technical_images\/26042-insights_image-general-efficiences-technical-blog-1-insights.jpg","field_partners":"","rxt_platforms":"Oracle, MySQL, Relational Databases","product":"","publisheddate":"2022-01-10T22:27:58","rxt_solutions":"","opengraph_tag":"","x_tag":"","teaser_flag":"Technical Blog","seo_titile":"Oracle Internet Directory Migration to Unified Directory","field_topics":"","field_slug":"oracle-internet-directory-migration-to-oracle-unified-directory","footnotes":""},"categories":[178],"tags":[204],"class_list":["post-6987","blogs","type-blogs","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-technical"],"_links":{"self":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs\/6987","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs"}],"about":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/types\/blogs"}],"author":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/comments?post=6987"}],"version-history":[{"count":2,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs\/6987\/revisions"}],"predecessor-version":[{"id":8658,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs\/6987\/revisions\/8658"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/media\/6989"}],"wp:attachment":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/media?parent=6987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/categories?post=6987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/tags?post=6987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
1. Synchronizing OUD with OID using DIP<\/h3>\n
$ dsreplication enable-changelog -h localhost -p 4444 -D \"cn=directory manager\" -j<\/code> pwd-file -r 8989 -b dc=example,dc=com -X -n<\/code><\/p>\nldapsearch -h <HOSTNAME> -p <PORT> -D \"cn=<DM_ADMIN>\" -w <PASSWORD> -s base -b \"\" <\/code> \"objectclass=*\" namingContexts<\/code> version: 1<\/code> dn:<\/code> namingContexts: cn=changelog<\/code> namingContexts: <SUFFIX_DN><\/code><\/p>\nENABLE SSL ON OID:<\/h4>\n
ldapbind -h <OID_HOSTNAME> -p <OID_PORT> -D \"cn=<OID_ADMIN>\" -w <PASSWORD> -U 2 <\/code> -W \"file:\/home\/oracle\/oid1_client_wallet\" -P \"<PASSWORD>\"<\/code> bind successful<\/code><\/p>\nDIP Configuration Steps<\/h3>\n
keytool -importcert -trustcacerts -file \/home\/oracle\/certificates_base\/ <\/code> oid1_selfsigned_cert.txt -keystore $HOME\/dip_keystore<\/code><\/p>\nTrust this certificate? [no]: yes<\/code><\/p>\nCertificate was added to keystore<\/code><\/p>\n$ORACLE_HOME\/bin\/manageDIPServerConfig set -attribute keystorelocation -h<\/code><\/p>\n<OID_HOSTNAME> -p <WLS_PORT> -D <WL_ADMIN> -value $HOME\/dip_keystore <wls admin <\/code><\/p>\nuser password><\/code><\/p>\nConnection parameters initialized. <\/code><\/p>\nConnected successfully. <\/code><\/p>\nThe attribute keystorelocation is successfully changed to value \/home\/oracle\/dip_keystore. <\/code><\/p>\n$ORACLE_HOME\/bin\/manageDIPServerConfig set -attribute sslmode -h <OID_HOSTNAME> -p <\/code><\/p>\n<WLS_PORT> -D <WLS_ADMIN> -value 2 <wls admin user password><\/code><\/p>\nConnection parameters initialized.<\/code><\/p>\nConnected successfully.<\/code><\/p>\nThe attribute sslmode is successfully changed to a value of 2.<\/code><\/p>\nwlst.sh<\/code><\/p>\nconnect('<WLS_ADMIN>','<PASSWORD>','t3:\/\/localhost:<EM_PORT>')<\/code><\/p>\ncreateCred(map=\"dip\",key=\"jksKey\", user=\"<JKS_USER>\",password=\"<PASSWORD>\")<\/code> disconnect()<\/code><\/p>\nSYNCHRONIZATION PROFILE OUD AND OID:<\/h4>\n
CREATE SYNCHRONIZATION PROFILE:<\/h4>\n
\u201cou=people, dc=people,dc=com\u201d<\/code> on each side as reflected in the following screenshot.<\/p>\nBOOTSTRAPPING DATA FROM OID TO OUD:<\/h4>\n
cat aci_oudimport.ldif <\/code> dn: ou=People,dc=people,dc=com <\/code> changetype :modify<\/code> add: orclaci<\/code> orclaci:access to entry by dn=\"orclodipagentname=OUDImport,cn=subscriber profile, <\/code> cn=changelog subscriber,cn=oracle internet directory\" (browse,add,delete)<\/code> orclaci: access to attr=(*) by group=\"orclodipagentname=OUDImport,cn=subscriber<\/code> profile,cn=changelog subscriber,cn=oracle internet directory\"<\/code> (read,search,write, selfwrite,compare) <\/code><\/p>\nldapmodify -h <OID_HOSTNAME> -p <OID_PORT> -D cn=<OID_ADMIN> -w <PASSWORD> -f <\/code> aci_oudimport.ldif <\/code><\/p>\nsyncProfileBootstrap -h <OID_HOSTNAME> -p <WLS_PORT> -D <WLS_ADMIN> -pf OUDImport<\/code><\/p>\nConnection parameters initialized.<\/code><\/p>\nConnecting at <OID_HOSTNAME>:<WLS_PORT>, with userid \"<WLS_ADMIN>\".<\/code><\/p>\nConnected successfully.<\/code><\/p>\nentries read in bootstrap operation: 1907<\/code><\/p>\nentries filtered in bootstrap operation: 0<\/code><\/p>\nentries ignored in bootstrap operation: 0<\/code><\/p>\nentries processed in bootstrap operation: 1906<\/code><\/p>\nentries failed in bootstrap operaton: 1<\/code><\/p>\nou=people,dc=people,dc=com<\/code><\/p>\nSchemasync<\/h3>\n
Syntax for Schemasync:<\/code><\/p>\nschemasync -srchost hostname -srcport port -srcdn bindDN -srcpwd password -dsthost<\/code><\/p>\nhostname -dstport port -dstdn bindDN -dstpwd password [-ldap]<\/code><\/p>\n-srchost \u2013 Host name of source directory server.<\/code><\/p>\n-srcport \u2013 Source directory source LDAP listening port<\/code><\/p>\n-srcdn \u2013 The DN of the user used to bind to the source directory.<\/code><\/p>\n-srcpwd \u2013 The user password used to bind to the source directory.<\/code><\/p>\n-dsthost \u2013 Host name of Destination directory server.<\/code><\/p>\n-destport \u2013 LDAP listening port for Destination directory server.<\/code><\/p>\n-dstdn \u2013 DN of the user used to bind to the destination directory server.<\/code><\/p>\n-ldap \u2013 When we use LDAP, Schema changes are applied directly from the source LDAP<\/code> to destination LDAP.<\/code><\/p>\nschemasync -srchost srchost.domain.com -srcport 3060 -srcdn \"cn=orcladmin\" \\ <\/code><\/p>\n-dsthost dsthost.domain.com -dstport 3060 \\<\/code><\/p>\n-dstdn \"uid=superuser,ou=people,dc=people,dc=com\" -ldap<\/code><\/p>\n <\/h3>\n
Conclusion:<\/h3>\n
\n![\"Managed](\"\/wp-content\/uploads\/2026\/blog_article_images\/26042-body-technical-blog-managed-oracle-applications-cta-image-1.png\")
\n<\/a>
\n![\"Managed](\"\/wp-content\/uploads\/2026\/blog_article_images\/26042-body-techncal-blog-managed-relational-databases-cta-image-1.png\")
\n<\/a><\/p>\n