An Oracle Database Advanced Replication-based replica cannot be a consumer of

C-12 Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory Task 1: Stop the Directory Replication Server on All Nodes To stop the directory replication server, run the following command on each node in the LDAP replication group: oidctl connect=connStr server=oidrepld instance=1 componentname=oidComponentName\ flags=-h LdapHost -p LdapPort stop Task 2: Identify a Sponsor Node and Install Oracle Internet Directory You must identify a sponsor node for this Task. It is the node that supplies the data to the new node. For the RMS, Oracle recommends that you install the new instance of Oracle Internet Directory as an Advanced Replication replica. You could use an existing master node as the RMS, but extra manual steps are required. Install a new Oracle Internet Directory on the remote site. If an existing master is used as RMS, you must follow the instructions in If an Existing Master is Used as a Remote Master Site on page C-5to migrate the masters metadata to the sponsor node. After successfully migrating the masters metadata to the MDS, you can now safely continue with Task 3: Switch the Sponsor Node to Read-Only Mode . Task 3: Switch the Sponsor Node to Read-Only Mode A sponsor node is the node that supplies the data to the new node. To switch the sponsor node from readwrite to read-only mode, use one of the procedures in Changing Server Mode on page 15-2 Task 4: Back up the Sponsor Node by Using ldifwrite Because this may take a long time, you may start Task 5: Perform Advanced Replication Add Node Setup while backup is in process. On the sponsor node, verify that ORACLE_INSTANCE is set, then enter the following command: ldifwrite connect=connect_string \ baseDN=orclAgreementID=000001,cn=replication configuration \ file=output_ldif_file This backs up the directory of the sponsor node. Task 5: Perform Advanced Replication Add Node Setup Note: While the sponsor node is in read-only mode, you may not make any updates to it. You may, however, update any of the other nodes, but those updates are not replicated immediately. Also, the sponsor node and the MDS may be the same node. Note: Oracle Net Service must be configured properly on all nodes for replication. See: On All Nodes, Prepare the Oracle Net Services Environment for Replication on page C-6. Setting Up Oracle Database Advanced Replication-Based Replication C-13 You can perform the Advanced Replication add node setup at the same time that you perform Task 4: Back up the Sponsor Node by Using ldifwrite on page C-12. On the sponsor node, enter this command: remtool -addnode The Replication Environment Management Tool adds the node to the DRG. Task 6: Switch the Sponsor Node to Updatable Mode To switch the sponsor node to updatable mode, use one of the procedures in Changing Server Mode on page 15-2. Task 7: Start the Directory Replication Server on All Nodes Except the New Node To start the directory replication server, type the following command on all nodes except the new node: oidctl connect=connStr server=oidrepld instance=1 componentname=oidComponentName \ flags=-h LdapHost -p LdapPort start To ensure that no directory or replication processes are running on the new node, type: opmnctl stopproc process-type=OID Note: When you run remtool -addnode to add the first Advanced Replication replica of a replication group, the tool does the initial replication setup for you, as if you had used remtool -asrsetup. You must specify the sponsor nodes connect identifier when you use remtool -addnode. When you use remtool -addnode, the operation might take a long time to complete, depending on the number of rows available in replicated tables and the network latency between the nodes. Use the -v option to view the progress of this operation. If you encounter errors, then use the -asrverify option first. If it reports errors, then rectify them by using the -asrrectify option. Both -asrverify and -asrrectify list all nodes in the DRG. If the new node is in the list, remove the new node by running the Replication Environment Management tool with -delnode option. Then add the new node again using the -addnode option. See Also: The remtool command-line reference in Oracle Fusion Middleware Reference for Oracle Identity Management for instructions on using the -addnode option of the Replication Environment Management Tool Note: Task 6 is very similar to Task 3. The only difference is that the orclservermode parameter is being set back to ReadWrite in this step. C-14 Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory Task 8: Load Data into the New Node by Using bulkload To load data, ensure that ORACLE_INSTANCE is set, then type the following command on the new node: bulkload connect=db_connect_string_of_new_node check=TRUE generate=TRUE \ load=TRUE restore=TRUE \ file=absolute_path_to_the_ldif_file_generated_by_ldifwrite Task 9: Start the Directory Server on the New Node To start the directory server, type the following command on the new node: opmnctl startproc process-type=OID Task 10: Start the Directory Replication Server on the New Node To start the directory replication server, type the following command on the new node: oidctl connect=connStr server=oidrepld instance=1 componentname=oidComponentName \ flags=-h LdapHost -p LdapPort start Deleting a Node from a Multimaster Replication Group At times, you may want to delete a node from a DRG for example, if the addition of a new node did not fully succeed as a result of system errors. To delete a replication node, perform the tasks described in these topics: ■ Task 1: Stop the Directory Replication Server on All Nodes ■ Task 2: Stop All Oracle Internet Directory Processes in the Node to be Deleted ■ Task 3: Delete the Node from the Master Definition Site ■ Task 4: Start the Directory Replication Server on All Nodes Note: If you load data from an earlier version of Oracle Internet Directory, such as 10g Release 2 10.1.2.0.2 onto a node running 10g 10.1.4.0.1, you must update the password policy entries as described in Password Policy and Fan-out Replication on page 38-28. Note: If you must change configuration or agreement parameters, see Chapter 41, Managing and Monitoring Replication . Notes: ■ If a directory server instance is participating in a replication agreement, do not use the bulkload tool to add data into the node. Instead, use ldapadd. ■ If Oracle Single Sign-On is desired in replication, then follow the postinstallation steps in the replication installation section of the Oracle Application Server Single Sign-On Administrators Guide in the 10g 10.1.4.0.1 library. Setting Up Oracle Database Advanced Replication-Based Replication C-15 Task 1: Stop the Directory Replication Server on All Nodes To stop the directory replication server, run the following command on each node in the DRG: oidctl connect=connStr server=oidrepld instance=1 componentname=oidComponentName \ flags=-h LdapHost -p LdapPort stop Task 2: Stop All Oracle Internet Directory Processes in the Node to be Deleted On the node to be deleted, shut down Oracle Internet Directory. opmnctl stopproc process-type=OID Task 3: Delete the Node from the Master Definition Site From the MDS, run the following script: remtool -delnode The Replication Environment Management Tool deletes the node from the replication group. This process can take a long time, depending on your system resources and the size of your DRG. If you use the -v option, the tool keeps you informed of its progress. Task 4: Start the Directory Replication Server on All Nodes To start the directory replication server, type the following command on each of the remaining nodes of the DRG: oidctl connect=connStr server=oidrepld instance=1 componentname=oidComponentName \ flags=-h LdapHost -p LdapPort start See Also: The opmn command-line tool reference in Oracle Fusion Middleware Reference for Oracle Identity Management for more information about shutting down Oracle Internet Directory. See Also: The remtool command-line tool reference in Oracle Fusion Middleware Reference for Oracle Identity Management for instructions on using the -delnode option of the Replication Environment Management Tool Note: If you encounter errors, then use the -asrverify option first. If it reports errors, then rectify them by using the -asrrectify option. Both -asrverify and -asrrectify list all nodes in the DRG. If the node to be deleted is in the list, then delete it by running the Replication Environment Management tool again, using the -delnode option. See Also: The opmn command-line tool reference in Oracle Fusion Middleware Reference for Oracle Identity Management