Perform the following steps before using the User Migration Utility:
Ensure that the directory server is running with SSL enabled for no authentication.
Ensure that the database server is running with encryption and integrity enabled.
Ensure that the database listener has a TCP listening end point.
Create an identity management realm in the directory, if it does not already exist.
Create the parent context for the user entries in the directory, if it does not already exist. The default (and recommended) location is in the orclcommonusercreatebase subtree in the common container in the Oracle Context.
Set up directory access for the database Oracle home by using Oracle Net Configuration Assistant to create an ldap.ora file. Note that the ldap.ora file must include the identity management realm DN so the utility can locate the correct administrative context. The utility searches for this file under $LDAP_ADMIN, $ORACLE_HOME/ldap/admin, $TNS_ADMIN, $ORACLE_HOME/network/admin, and, finally, the Domain Name System (DNS) server, if you are using DNS discovery. (See Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory for information about DNS server discovery.)
Note:
If you plan to use shared schema mapping when migrating users, then you must create the shared schema before running this utility.
The same ldap.ora file must be used for both Phase One and Phase Two of a user migration.
See Also:
Enterprise User Security Configuration Tasks and Troubleshooting for detailed information about setting up enterprise user authentication after the user migration is finished
Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory