Create an LDIF file similar to this:

Managing Replication Configuration Attributes 40-5 Oracle Database Advanced Replication-Based Replication Agreements For Advanced Replication, the replication agreement on each node lists all of the nodes in the group. It is identical on each node except for local options such as partitioned naming contexts on the local directory server. The entry for this kind of replication agreement resides immediately below the cn=replication configuration container entry. For example, the DN of such an agreement can look like this: orclagreementID=000001,cn=replication configuration. LDAP Replication Agreements For LDAP-based replication, there are separate replication agreements for each supplier-consumer relationship. For one-way replication, there is a single, one-way replication agreement. The entry for an LDAP-based replication agreement resides immediately below the replica subentry of the node that serves as the supplier. Thus, the DN of the replication agreement as found on a supplier node is: orclagreementID=unique_identifier_of_the_replication_agreement, orclReplicaID=unique_identifier_of_supplier_node, cn=replication configuration Similarly, the DN of the replication agreement as found on a consumer node is: orclagreementID=unique_identifier_of_the_replication_agreeement, orclReplicaID=unique_identifier_of_supplier_node, cn=replication configuration In a fan-out replication agreement, you can tell which node the agreement entry is associated with by looking at its parent. For example, look at the following replication agreement entry. orclagreementID=000002,orclReplicaID=node_A,cn=replication configuration In this example, you can determine that the replication agreement represented by orclagreementID=000002 is associated with node A. This is because the parent of orclagreementID=000002 is orclReplicaID=node_A. Two-Way LDAP Replication Agreements For two-way replication, there can be either a single, two-way replication agreement or two one-way agreements for each supplier-consumer relationship. The following is a sample two-way replication agreement entry: dn: orclagreementid=000002, orclreplicaid=stadd58_repl, cn=replication configuration Notes: ■ The container entry cn=replication configuration is replicated on all nodes, but may not be identical on all nodes. ■ The orclreplicadn attribute of an LDAP-based replication agreement specifies the associated consumer node. ■ The agreementtype indicates the replication agreement type. See Table 40–2, Attributes of the Replication Agreement Entry for values of orclagreementtype.