JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Directory Server Enterprise Edition Administration Guide 11g Release 1 (
search filter icon
search icon

Document Information


Part I Directory Server Administration

1.  Directory Server Tools

2.  Directory Server Instances and Suffixes

3.  Directory Server Configuration

4.  Directory Server Entries

5.  Directory Server Security

6.  Directory Server Access Control

7.  Directory Server Password Policy

8.  Directory Server Backup and Restore

9.  Directory Server Groups, Roles, and CoS

10.  Directory Server Replication

Planning Your Replication Deployment

Recommended Interface for Configuring and Managing Replication

Summary of Steps for Configuring Replication

Summary of Steps for Configuring Replication

Enabling Replication on a Dedicated Consumer

To Create a Suffix for a Consumer Replica

To Enable a Consumer Replica

To Perform Advanced Consumer Configuration

Enabling Replication on a Hub

To Create a Suffix for a Hub Replica

To Enable a Hub Replica

To Modify Change Log Settings on a Hub Replica

Enabling Replication on a Master Replica

To Create a Suffix for a Master Replica

To Enable a Master Replica

To Modify Change Log Settings on a Master Replica

Configuring the Replication Manager

Using a Non-Default Replication Manager

To Set A Non-Default Replication Manager

To Change the Default Replication Manager Password

Creating and Changing Replication Agreements

To Create a Replication Agreement

To Change the Destination of a Replication Agreement

Fractional Replication

Considerations for Fractional Replication

To Configure Fractional Replication

Replication Priority

To Configure Replication Priority

Initializing Replicas

To Initialize a Replicated Suffix from a Remote (Supplier) Server

Replica Initialization From LDIF

To Initialize a Replicated Suffix From LDIF

To Export a Replicated Suffix to LDIF

Filtering an LDIF File for Fractional Replication

Initializing a Replicated Suffix by Using Binary Copy

Restrictions for Using Binary Copy With Replication

Making a Binary Copy for Initializing a Server

Initializing Replicas in Cascading Replication

To Initialize Replicas in Cascading Replication

Indexing Replicated Suffixes

Incrementally Adding Many Entries to Large Replicated Suffixes

To Add Many Entries to Large Replicated Suffixes

Replication and Referential Integrity

Replication Over SSL

To Configure Replication Operations for SSL

To Configure Client Authentication Based Replication for SSL

Replication Over a WAN

Configuring Network Parameters

Configuring Window Size

Configuring Group Size

Scheduling Replication Activity

To Schedule Replication Activity

Configuring Replication Compression

To Configure Replication Compression

Modifying the Replication Topology

Changing the Replication Manager

Managing Replication Agreements

Disabling a Replication Agreement

Enabling a Replication Agreement

Deleting a Replication Agreement

Promoting or Demoting Replicas

To Promote or Demote a Replica

Disabling a Replicated Suffix

To Disable a Replicated Suffix

Keeping Replicated Suffixes Synchronized

Replication Retry Algorithm

To Force Replication Updates

Moving a Master Replica to a New Machine

To Remove a Master From an Existing Replication Topology

To Add a Master to an Existing Replication Topology

Replication With Releases Prior to Directory Server 11g Release 1 (

Replicating Between Directory Server 11g Release 1 ( and Directory Server 6 or 5.2

Using the Retro Change Log

To Enable the Retro Change Log

To Configure the Retro Change Log to Record Updates for Specified Suffixes

To Configure the Retro Change Log to Record Attributes of a Deleted Entry

To Trim the Retro Change Log

Access Control and the Retro Change Log

Getting Replication Status

Getting Replication Status in DSCC

Getting Replication Status by Using the Command Line

Solving Common Replication Conflicts

Solving Replication Conflicts by Using DSCC

Solving Replication Conflicts by Using the Command Line

Solving Naming Conflicts

To Rename a Conflicting Entry That has a Multivalued Naming Attribute

To Rename a Conflicting Entry With a Single-Valued Naming Attribute

Solving Orphan Entry Conflicts

Solving Potential Interoperability Problems

11.  Directory Server Schema

12.  Directory Server Indexing

13.  Directory Server Attribute Value Uniqueness

14.  Directory Server Logging

15.  Directory Server Monitoring

Part II Directory Proxy Server Administration

16.  Directory Proxy Server Tools

17.  Directory Proxy Server Instances

18.  LDAP Data Views

19.  Directory Proxy Server Certificates

20.  Directory Proxy Server Load Balancing and Client Affinity

21.  Directory Proxy Server Distribution

22.  Directory Proxy Server Virtualization

23.  Virtual Data Transformations

24.  Connections Between Directory Proxy Server and Back-End LDAP Servers

25.  Connections Between Clients and Directory Proxy Server

26.  Directory Proxy Server Client Authentication

27.  Directory Proxy Server Logging

28.  Directory Proxy Server Monitoring and Alerts

Part III Directory Service Control Center Administration

29.  Directory Service Control Center Configuration


Creating and Changing Replication Agreements

A replication agreement is a set of parameters on a supplier that configures and controls how updates are sent to a given consumer. The replication agreement must be created on the supplier replicated suffix that is sending updates to its consumer. You must create a replication agreement on the supplier for every consumer that you want updated.

To Create a Replication Agreement

You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.

If you use DSCC to create a new replication agreement, you can choose to copy some or all replication agreement configuration settings from an existing replication agreement.

  1. From your master server, create a replication agreement for each consumer that you want to replicate to.
    $ dsconf create-repl-agmt -h host -p port suffix-DN consumer-host:consumer-port\

    For example:

    $ dsconf create-repl-agmt -h host1 -p 1389 dc=example,dc=com host2:1389

    To list existing replication agreements by using the command line, use the dsconf list-repl-agmts command.

    Note - If you change the port number on a master when replication is running, you do not need to reinitialize the servers. However, the old replication agreement that pointed to the old address (host:old-port) is no longer useful. If you want replication to continue as it did before the port number was changed, you must create a new agreement with the new address (host:new-port).

  2. Check that the replication agreement has been created correctly.
    $ dsconf show-repl-agmt-status -h host -p port suffix-DN consumer-host:consumer-port
  3. If the authentication status is not OK, run the dsconf accord-repl-agmt command.

    Note - Only use the command dsconf accord-repl-agmt if you are using the default replication manager. If you have created a new replication manager, do not use this command because it overwrites some required settings.

    The dsconf accord-repl-agmt command ensures that both the supplier and destination servers share the same replication authentication settings.

    $ dsconf accord-repl-agmt -h host -p port suffix-DN consumer-host:consumer-port

    For example:

    $ dsconf accord-repl-agmt -h host2 -p 1389 dc=example,dc=com host1:1389

To Change the Destination of a Replication Agreement

This procedure changes the remote replica pointed to by an existing replication agreement. The suffix DN and configuration of the existing agreement remain the same.