Oracle by Example brandingMigrating the Directory Data to Oracle Unified Directory 12c

section 0Before You Begin

This 10-minute tutorial shows you how to import the data into the Oracle Unified Directory and execute the migration tasks.

This is the third tutorial in the series Migrating Oracle Directory Server Enterprise Edition 11g Directly to Oracle Unified Directory 12c. Read them sequentially.

Background

To migrate from ODSEE to OUD, the ODSEE data exported to the LDIF format has to be imported to the Oracle Unified Directory.

What Do You Need?

Perform the tasks described in Migrating the Oracle Directory Server Enterprise Edition 11g Schema and Configuration to Oracle Unified Directory 12c

section 1Import Directory Data to OUD

In this section, you'll populate the OUD server back end with the data read from an LDIF file.

  1. Stop the OUD server before you import the LDIF data.
    2. $ cd $OUD_INSTANCE/bin
 ./stop-ds
Stopping Server...

[18/Jan/2018:02:40:18 -0800] category=CORE severity=NOTICE msgID=9896307  msg=The Directory Server is now stopped
  2. On the OUD server, import the LDIF data.
    3. $ ./import-ldif -b dc=example,dc=com -l /u01/app/oracle/product/odsee/dsee7/odsee_instances/dsinst/ldif/odsee-data.ldif

    You should see an output similar to the following:

    [18/Jan/2018:02:43:05 -0800] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381717 msg=Installation Directory:  /u01/app/oracle/product/oud/oud
[18/Jan/2018:02:43:05 -0800] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381719 msg=Instance Directory:      /u01/app/oracle/config/oud_instances/oud1/OUD
[18/Jan/2018:02:43:05 -0800] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381713 msg=JVM Information: 1.8.0_144-b01 by Oracle Corporation, 64-bit architecture, 5905580032 bytes heap size
....
....
....
[18/Jan/2018:02:43:07 -0800] category=JEB severity=NOTICE msgID=8847454 msg=Processed 160 entries, imported 160, skipped 0, rejected 0 and migrated 0 in 0 seconds (average rate 175.2/sec)
  3. Restart the OUD Server.
    4. $ ./start-ds
[18/Jan/2018:02:44:55 -0800] category=CORE severity=INFORMATION msgID=132 msg=The Directory Server is beginning the configuration bootstrapping process
[18/Jan/2018:02:44:56 -0800] category=CORE severity=NOTICE msgID=458886 
....
....
....
[18/Jan/2018:02:45:00 -0800] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887):  The Directory Server has started successfully

section 2Verify the Migration

In this section you'll verify the migration by using the ldapsearch command.

  1. Search for an entry in the ODSEE instance by using the ldapsearch command.
    2. $ ldapsearch -p 21389 -h host01.example.com -b "dc=example,dc=com" -D "cn=Directory Manager" -w password "(uid=ajensen)" mail
# LDAPv3
# base  with scope subtree
# filter: (uid=ajensen)
# requesting: mail 
# ajensen, People, example.com
dn: uid=ajensen, ou=People, dc=example,dc=com
mail: ajensen@example.com
 # search result
  2. Verify the same changes in the OUD instance by using the ldapsearch command.
    3. $ ldapsearch -p 20389 -h host01.example.com -b "dc=example,dc=com" -D "cn=Directory Manager" -w password "(uid=ajensen)" mail
# LDAPv3
# base  with scope subtree
# filter: (uid=ajensen)
# requesting: mail 
# ajensen, people, example.com
dn: uid=ajensen,ou=people,dc=example,dc=com
mail: ajensen@example.com
# search result

    Conclusion: Once you complete the application testing and the client applications are redirected to OUD, you stop the coexistence between the two environments. You deprovision and uninstall the ODSEE. Transition from ODSEE 11g to OUD 12c by Direct Migration method is now complete.

more informationWant to Learn More?