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
7. Migrating a Replicated Topology
Overview of Migrating Replicated Servers
Issues Related to Migrating Replicated Servers
Issues With the Password Policy
Migration of Replication Agreements
Manual Reset of Replication Credentials
Problems Related to Tombstone Purging
Migrating a Replicated Topology to an Identical Topology
Migrating a Replicated Topology to a New Topology
Migrating Over Multiple Data Centers
8. Architectural Changes in Directory Server Since Version 5.2
9. Migrating Directory Proxy Server
Directory Server 11g Release 1 (11.1.1.5.0) does not limit the number of masters in a multi-master topology. A fully-meshed, multi-master topology with no hubs or consumers is recommended in most cases.
Advantages of an all-master topology include the following:
Availability. Write traffic is never disrupted if one of the servers goes down.
Simplicity. In an all-master topology, there is no need to set up referrals to route reads and writes to different servers.
There may be reasons that an all-master topology is not viable in a specific deployment. For example, fractional replication cannot be used in an all-master topology because fractional replication is only supported from masters to consumers.