JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Fusion Middleware Administration Guide for Oracle Unified Directory 11g Release 1 (11.1.1)
search filter icon
search icon

Document Information


1.  Starting and Stopping the Server

2.  Configuring the Server Instance

3.  Configuring the Proxy Components

4.  Configuring Security Between Clients and Servers

5.  Configuring Security Between the Proxy and the Data Source

6.  Managing Oracle Unified Directory With Oracle Directory Services Manager

7.  Managing Directory Data

8.  Replicating Directory Data

Configuring Data Replication With dsreplication

To Enable Replication Between Two Servers

To Initialize a Replicated Server

To Initialize an Entire Topology

To Test Replication

To Obtain the Status of a Replicated Topology

To Merge Two Existing Replicated Topologies

To Disable Replication For a Specific Replication Domain

Configuring Large Replication Topologies

To Configure a Dedicated Replication Server

Modifying the Replication Configuration With dsconfig

Retrieving the Replication Domain Name

Changing the Replication Purge Delay

How Replication Changes Are Purged

To Change the Replication Purge Delay

Changing the Window Size

To Change the Window Size

Changing the Initialization Window Size

To Change the Initialization Window Size

Changing the Heartbeat Interval

To Change the Heartbeat Interval

Changing the Isolation Policy

To Change the Isolation Policy

Configuring Encrypted Replication

To Configure Encrypted Replication

Configuring Replication Groups

To Configure a Replication Group

Configuring Assured Replication

To Configure Assured Replication in Safe Data Mode

To Configure Assured Replication in Safe Read Mode

Configuring Fractional Replication

To Configure Exclusive Fractional Replication

To Configure Inclusive Fractional Replication

To Configure and Initialize a Fractional Domain

Configuring Replication Status

To Configure the Degraded Status Threshold

Configuring the Replication Server Weight

Initializing a Replicated Server With Data

Initializing a Single Replicated Server

Initializing a New Replicated Topology

Adding a Directory Server to an Existing Replicated Topology

Changing the Data Set in an Existing Replicated Topology

To Change the Data Set With import-ldif or Binary Copy

Appending Data in an Existing Replicated Topology

Using the External Change Log

Enabling the External Change Log in Oracle Unified Directory

External Change Log APIs

How a Client Application Uses the External Change Log in Cookie Mode

Format of External Change Log Entries

To Specify the Attributes to be Included in the External Change Log

Initializing Client Applications to Use the External Change Log

To Initialize a Client Application to Use the External Change Log

Reinitializing a Client Application When a Domain is Added

Reinitializing a Client Application When a Domain is Removed or Disabled

Controlling Access to the External Change Log

Purging the External Change Log

To Disable the External Change Log for a Domain

Configuring Schema Replication

Specifying the Schema Source

Disabling Schema Replication

To Specify That Schema Should Not Be Replicated

To Disable Schema Replication

Replicating to a Read-Only Server

To Configure a Replica as Read-Only

Detecting and Resolving Replication Inconsistencies

Types of Replication Inconsistencies

Detecting Inconsistencies

Resolving Inconsistencies

Solving Naming Conflicts

Purging Historical Replication Data

Using Isolated Replicas

Deployment Scenarios for Isolated Replicas

Using Isolated Replicas in a DMZ

Using Isolated Replicas for Testing

Replicating Between Oracle Directory Server Enterprise Edition and Oracle Unified Directory

To Migrate the Oracle Directory Server Enterprise Edition Schema and Configuration

To Initialize the Oracle Unified Directory with Oracle Directory Server Enterprise Edition Data

To Configure Replication Between Oracle Directory Server Enterprise Edition and Oracle Unified Directory

9.  Controlling Access To Data

10.  Managing Users and Groups With dsconfig

11.  Managing Password Policies

12.  Managing Directory Schema

13.  Monitoring Oracle Unified Directory

14.  Tuning Performance

15.  Advanced Administration

Purging Historical Replication Data

Oracle Unified Directory maintains a history of all changes that have been made on the server as a result of replication operations. This historical replication data is stored in an attribute of each user entry, and can eventually take up a large amount of space on your disk. Historical information is therefore purged when an entry is modified, or when you specifically run a command to purge the data.

By default, information that is older than one day is purged. You can specify the age of data that should be purged by setting the value of the conflicts-historical-purge-delay property of the replication domain. The following example specifies that data older than five days should be purged. Note that the value of the property is expressed in minutes.

$ dsconfig -h localhost -p 4444 -D "cn=directory manager" -w password -X -n \
  set-replication-domain-prop --provider-name "Multimaster Synchronization" \
  --domain-name dc=example,dc=com --set conflicts-historical-purge-delay:7200m

You can also purge historical data immediately, or schedule a task to purge the data at a specific time. Imagine, for example, that you initialize a server with a large number of entries, then perform a significant number of changes on these entries. The resulting replication historical data will increase the size of the database quite substantially. If your server is then used mainly for read operations, the large database size remains, because no modifications are made to trigger a purge of the historical data. In this case, you can launch a once off purge task to remove the historical data that was generated by the initial modifications, and return the database to a more accurate size.

Because the purge process can take some time, you are required to specify the maximum duration of the purge (in seconds). To purge historical data immediately, run the following command:

$ dsreplication -h localhost -p 4444 --adminUID admin --adminPassword password \
  purge-historical --maximumDuration 3600 --baseDN dc=example,dc=com -X -n

For information about scheduling commands as tasks, see Configuring Commands As Tasks.