The Novell® eDirectoryTM Merge utility allows you to merge two separate Novell eDirectory trees into a single eDirectory tree. Only the Tree objects are merged; container objects and their leaf objects maintain separate identities within the newly merged tree.
HINT: To move leaf objects or merge partitions, use ConsoleOne® or Novell iManager.
The two trees you merge are called the local source tree and the target tree. Before merging one tree into another tree, the target tree should have all but one replica of the root partition removed. When there is only one replica of the root partition in the target tree, you can proceed with the merge. After the merge, there will be two replicas of the root partition-the replica that was on the target tree and the replica that was on the source tree server that ran the merge operation. If you need additional replicas of the root partition in your tree, you can place them after the merge has completed.
If the target tree server contains more than one replica of the root partition when the merge takes place, servers not holding the master replica might have a problem with the placement of external reference objects. These objects are contained in subordinate reference partition roots that must be placed on the other servers that have a replica of the root partition to represent partition boundaries. For each partition subordinate to the root partition in the source tree, there must be a subordinate reference partition root placed in the target tree. If there is a failure, it will report an eDirectory error code of -605 for synchronization status. In this case, use DSRepair to run a local database repair on the server producing the error. See Performing a Local Database Repair for more information.
DSMerge does not change eDirectory names or contexts within the containers. Object and property rights for the merged objects are retained.
This chapter contains the following topics: