Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Upgrade and Migration Guide 11 g Release 1 (11.1.1.5.0) |
Part I Patching Directory Server Enterprise Edition 7 to 11g Release 1 (11.1.1.5.0)
2. Patching Directory Server Enterprise Edition 7 to Version 11g Release 1 (11.1.1.5.0)
Part II Upgrading Directory Server Enterprise Edition 6 to 11g Release 1 (11.1.1.5.0)
3. Upgrading Directory Server Enterprise Edition 6 to Version 11g Release 1 (11.1.1.5.0)
Part III Migrating Directory Server Enterprise Edition 5.2 to Version 11g Release 1 (11.1.1.5.0)
4. Overview of the Migration Process for Directory Server
5. Automated Migration Using the dsmig Command
6. Migrating Directory Server Manually
Migrating Configuration Data Manually
Migration of Specific Configuration Attributes
Global Configuration Attributes
Security Configuration Attributes
Feature Configuration Attributes
Mapping Tree Configuration Attributes
Replication Configuration Attributes
Password Policy Configuration Attributes
UniqueID Generator Configuration Attributes
Database Configuration Attributes
Plug-In Configuration Attributes
Migrating Security Settings Manually
Migrating User Plug-Ins Manually
Tasks to be Performed After Manual Migration
7. Migrating a Replicated Topology
8. Architectural Changes in Directory Server Since Version 5.2
9. Migrating Directory Proxy Server
Migrating an instance manually involves migrating each part of the server in the same order as performed by the automatic migration tool (dsmig). In this section, old instance refers to the version 5.2 instance and new instance refers to the 11g Release 1 (11.1.1.5.0) instance.
Before you start a manual migration, ensure that the following tasks have been performed:
Directory Server 11g Release 1 (11.1.1.5.0) software has been installed.
Directory Server 11g Release 1 (11.1.1.5.0) software can be installed on the same machine that holds the Directory Server 5.2 instance, or on a different machine.
The new instance has been created.
The new instance can be created anywhere except for the exact location of the old instance. The new instance can be installed on the same LDAP/LDAPS port or on a different port. If you use different ports, any replication agreements to the new instance must be changed accordingly.
While creating a new instance, a DN and a password for the directory manager is stored in nsslapd-rootdn and nssalpd-rootpw attributes under cn=config. During the migration process, the values for these attributes from the old instance are not propagated as these attributes already hold a value for the new instance. The same behavior is applied to nsslapd-secureport and nsslapd-port attributes for the same reason.
The old instance has been stopped correctly.
A disorderly shutdown of the old instance will cause problems during migration. Even if the old and new instances are on different machines, the old instance must be stopped before migration is started.