|
Oracle® Identity Management User Reference
10g Release 2 (10.1.2) B15883-01 |
|
 Previous |
 Next |
|
Oracle® Identity Management User Reference
10g Release 2 (10.1.2) B15883-01 |
|
|
Previous |
Next |
The Replication Environment Management Tool is used to manage Oracle Internet Directory replication configuration activities.
More specifically, the Replication Environment Management tool:
Configures Oracle Database Advanced Replication-based multimaster replication.
Scans the replication environment and verifies an Oracle Database Advanced Replication-based directory replication group (DRG).
Rectifies any problems in an Advanced Replication-based DRG. If the tool cannot rectify a problem, it reports the point or points of failure, which you can then fix manually.
Reports queue statistics, deferred transactions errors, and administrative request errors of an Advanced Replication-based DRG.
Reconfigures the Advanced Replication-based DRG.
Configures LDAP-based replication.
Reconfigures an LDAP-based directory replication group (DRG).
operation
Required. The name of the operation to perform using remtool. See the appropriate operation documentation for operation specific syntax, arguments, and usage. The following operations are available:
addnode - Adds a new node to an Oracle Database Advanced Replication-based directory replication group (DRG). See "The remtool -addnode Operation" for more information about this operation.
asrcleanup - Cleans up the set up of an Oracle Database Advanced Replication-based DRG. See "The remtool -asrcleanup Operation" for more information about this operation.
asrrectify - Verifies the setup of Oracle Database Advanced Replication-based DRG, and corrects any problems found. See "The remtool -asrrectify Operation" for more information about this operation.
asrsetup - Creates a new directory replication group (DRG) by configuring Oracle Database Advanced Replication. See "The remtool -asrsetup Operation" for more information about this operation.
asrverify - Verifies the setup of Oracle Database Advanced Replication-based DRG, and reports any problems found. See "The remtool -asrverify Operation" for more information about this operation.
backupmetadata - Adds the metadata of a pilot replica to a master replica or backs up the metadata of a pilot replica into a file. This operation must be executed at the pilot replica. See "The remtool -backupmetadata Operation" for more information about this operation.
chgpwd - Changes the replication administrator's database account password on all nodes of an Oracle Database Advanced Replication-based DRG. See "The remtool -chgpwd Operation" for more information about this operation.
delnode - Deletes a node from an existing Oracle Database Advanced Replication-based DRG. See "The remtool -delnode Operation" for more information about this operation.
dispasrerr - Displays all deferred transaction errors and administrative request errors for an Oracle Database Advanced Replication-based DRG. See "The remtool -dispasrerr Operation" for more information about this operation.
dispqstat - Displays the queue statistics of all nodes in an Oracle Database Advanced Replication-based DRG. See "The remtool -dispqstat Operation" for more information about this operation.
paddnode - Adds a partial replica to an LDAP-based DRG. See "The remtool -paddnode Operation" for more information about this operation.
pchgpwd - Changes the password of a replication DN for a replica in an LDAP-based DRG. See "The remtool -pchgpwd Operation" for more information about this operation.
pchgwalpwd - Changes the wallet password of a replication DN for a replica in an LDAP-based DRG. See "The remtool -pchgwalpwd Operation" for more information about this operation.
pcleanup - Cleans up the partial replication setup of an LDAP-based DRG. See "The remtool -pcleanup Operation" for more information about this operation.
pdelnode - Deletes a partial replica from an LDAP-based DRG. See "The remtool -pdelnode Operation" for more information about this operation.
pilotreplica - Begins or ends pilot mode for a replica. See "The remtool -pilotreplica Operation" for more information about this operation.
presetpwd - Resets the password of a replication DN for a replica in an LDAP-based DRG. See "The remtool -presetpwd Operation" for more information about this operation.
resumeasr - Resumes replication activity for an Oracle Database Advanced Replication-based DRG. See "The remtool -resumeasr Operation" for more information about this operation.
suspendasr - Suspends replication activity for an Oracle Database Advanced Replication-based DRG. See "The remtool -suspendasr Operation" for more information about this operation.
-v
Optional. Runs the command in verbose mode. Shows detailed output for the command on the screen and also logs all operations in the remtool.log file created in $ORACLE_HOME/ldap/log.
The addnode operation adds a new node to an existing directory replication group (DRG). You must first create the DRG using "The remtool -asrsetup Operation". The following usage rules apply to this operation:
The node to be added must be empty.
You will need to know the SYSTEM user password of the new node.
Oracle Internet Directory processes on the master definition site (MDS) and other remote master sites (RMSs) must be down.
After the addnode operation is complete, Oracle Internet Directory processes can be restarted.
remtool -addnode [-connect repl_admin_name/password@net_service_name] [-v]
The tool will also prompt you for the database global name (as defined in the tnsnames.ora file) and SYSTEM password for each node to be added.
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the addnode operation you can perform the following tasks:
In this example, MY_HOST3.MY_COMPANY.COM is added to a DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM.
Example:
remtool -addnode -v -connect repadmin/repadmin@MY_HOST1.MY_COMPANY.COM
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS. MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid2 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ---- Do you want to continue? [y/n] : y ------------------------------------------------------------------------------ WARNING: Make sure that the replication administrator database account does not exist already in the new node to be added to the DRG. If the account exists, that account will be dropped and will be created newly. ------------------------------------------------------------------------------ Enter global name of new node to be added : MY_HOST3.MY_COMPANY.COM Enter SYSTEM user password of new node to be added : ------------------------------------------------------------------------------ Adding a new node... MY_HOST3.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST3.MY_COMPANY.COM : Dropping replication administrator repadmin... MY_HOST3.MY_COMPANY.COM : Creating replication administrator repadmin... MY_HOST3.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST3.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST3.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST3.MY_COMPANY.COM : Dropping replication group LDAP_REP... MY_HOST3.MY_COMPANY.COM : Creating purge job... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Creating database link to MY_HOST1.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Scheduling push job to MY_HOST1.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Creating database link to MY_HOST2.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Scheduling push job to MY_HOST2.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Creating database link to MY_HOST3.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Scheduling push job to MY_HOST3.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Creating database link to MY_HOST3.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Scheduling push job to MY_HOST3.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Quiescing replication activity... MY_HOST1.MY_COMPANY.COM : Adding replication site MY_HOST3.MY_COMPANY.COM to replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST3.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST3.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Resuming replication activity... MY_HOST1.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST2.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST3.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST1.MY_COMPANY.COM : Verifying replication agreement entry... MY_HOST1.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid3... CORRECTED: MY_HOST1.MY_COMPANY.COM : "my_host_rid3" hostname has been added to replication agreement entry. MY_HOST2.MY_COMPANY.COM : Verifying replication agreement entry... MY_HOST2.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid3... CORRECTED: MY_HOST2.MY_COMPANY.COM : "my_host_rid3" hostname has been added to replication agreement entry. MY_HOST3.MY_COMPANY.COM : Verifying replication agreement entry... MY_HOST3.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid... CORRECTED: MY_HOST3.MY_COMPANY.COM : "my_host_rid" hostname has been added to replication agreement entry. MY_HOST3.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid2... CORRECTED: MY_HOST3.MY_COMPANY.COM : "my_host_rid2" hostname has been added to replication agreement entry. MY_HOST3.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid3... CORRECTED: MY_HOST3.MY_COMPANY.COM : "my_host_rid3" hostname has been added to replication agreement entry. MY_HOST1.MY_COMPANY.COM : Verifying initialization parameter... MY_HOST2.MY_COMPANY.COM : Verifying initialization parameter... MY_HOST3.MY_COMPANY.COM : Verifying initialization parameter... ------------------------------------------------------------------------------ Node MY_HOST3.MY_COMPANY.COM has been added to this DRG. ------------------------------------------------------------------------------ Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS rid3 my_host MY_HOST3.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid3 RMS -------- ------------- ----------------------- ------------- ------------- ----
The asrcleanup operation cleans up an existing Oracle Database Advanced Replication setup. You must know the system password of all nodes taking part in the directory replication group (DRG) to run this operation.
remtool -asrcleanup [-connect repl_admin_name/password@net_service_name] [-v]
The tool will prompt you for the SYSTEM user password for each MDS and RMS node in the DRG
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the asrcleanup operation you can perform the following tasks:
In this example, setup is cleaned up for a DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM. The tool prompts you to enter the system password for each site.
Example:
remtool -asrcleanup -v
The results are:
Enter replication administrator's name : repadmin Enter replication administrator's password : Enter global name of MDS : my_host1.my_company.com MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS. MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ---- Do you want to continue? [y/n] : y ------------------------------------------------------------------------------ Cleaning up... MY_HOST1.MY_COMPANY.COM : Dropping replication site MY_HOST2.MY_COMPANY.COM from replication group LDAP_REP... MY_HOST2.MY_COMPANY.COM : Dropping replication group LDAP_REP... MY_HOST2.MY_COMPANY.COM : Unscheduling push job to MY_HOST1.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... Enter "SYSTEM" user password for "MY_HOST2.MY_COMPANY.COM" database at "my_host" host : MY_HOST2.MY_COMPANY.COM : Dropping replication administrator repadmin... MY_HOST1.MY_COMPANY.COM : Dropping replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Unscheduling push job to MY_HOST2.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MYCOMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... Enter "SYSTEM" user password for "MY_HOST1.MY_COMPANY.COM" database at "my_host" host : MY_HOST1.MY_COMPANY.COM : Dropping replication administrator repadmin... ------------------------------------------------------------------------------ ASR setup has been cleaned up. ------------------------------------------------------------------------------
The asrrectify operation is used for detecting and rectifying problems in an Oracle Database Advanced Replication-based DRG setup. It reports on errors and corrects them. Oracle Corporation recommends that, before running this operation, you stop Oracle Internet Directory servers.To use the asrrectify operation, all nodes in the DRG must be up and running. The operation will fail if any of the nodes are not running.If necessary, the asrrectify operation prompts for the SYSTEM user password.
remtool -asrrectify [-connect repl_admin_name/password@net_service_name] [-v]
The tool may also prompt you for the SYSTEM user password for each MDS and RMS node in the DRG.
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the asrrectify operation you can perform the following tasks:
In this example, setup errors are deducted and rectified in a DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM. The tool detects that a user has changed global name of MY_HOST2.MY_COMPANY.COM to NEWNAME.MY_COMPANY.COM after setting up Advanced Replication. It rectifies this error first before continuing with other checks.
Example:
remtool -asrrectify -v -conn repadmin/repadmin@my_host1.my_company.com
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS.
Enter "SYSTEM" user password for "MY_HOST2.MY_COMPANY.COM" database at "my_host" host :
NEWNAME.MY_COMPANY.COM : Renaming global name to MY_HOST2.MY_COMPANY.COM (instance name : rid2, hostname : my_host)
CORRECTED:
MY_HOST2.MY_COMPANY.COM : Global name of database "rid2" at host "my_host" has been changed to MY_HOST2.MY_COMPANY.COM.
MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS.
CORRECTED:
MY_HOST2.MY_COMPANY.COM : Global name of database "rid2" at host "my_host" has been changed to MY_HOST2.MY_COMPANY.COM.
Directory Replication Group (DRG) details :
-------- ------------- ----------------------- ------------- ------------- ----
Instance Host Name Global Name Version Replicaid Site
Name Type
-------- ------------- ----------------------- ------------- ------------- ----
rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS
rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS
-------- ------------- ----------------------- ------------- ------------- ----
Do you want to continue? [y/n] : y
------------------------------------------------------------------------------
Rectifying ASR setup...
MY_HOST1.MY_COMPANY.COM : Verifying initialization parameter...
MY_HOST2.MY_COMPANY.COM : Verifying initialization parameter...
MY_HOST1.MY_COMPANY.COM : Verifying replication administrator roles...
MY_HOST2.MY_COMPANY.COM : Verifying replication administrator roles...
MY_HOST1.MY_COMPANY.COM : Verifying database links...
MY_HOST2.MY_COMPANY.COM : Verifying database links...
MY_HOST1.MY_COMPANY.COM : Verifying purge job...
MY_HOST2.MY_COMPANY.COM : Verifying purge job...
MY_HOST1.MY_COMPANY.COM : Verifying scheduled links...
MY_HOST2.MY_COMPANY.COM : Verifying scheduled links...
MY_HOST1.MY_COMPANY.COM : Verifying availability of replication objects...
MY_HOST2.MY_COMPANY.COM : Verifying availability of replication objects...
MY_HOST1.MY_COMPANY.COM : Verifying replication group...
MY_HOST1.MY_COMPANY.COM : Resuming replication activity...
MY_HOST2.MY_COMPANY.COM : Verifying replication group...
MY_HOST1.MY_COMPANY.COM : Resuming replication activity...
MY_HOST1.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry...
MY_HOST2.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry...
MY_HOST1.MY_COMPANY.COM : Verifying replication agreement entry...
MY_HOST2.MY_COMPANY.COM : Verifying replication agreement entry...
-------------------- ----- ----- ----- ----- ----- ----- -----
DB Name Init Repl DB Purge Sch. Repl Repl
Param Admin Links Job Links Group Agrmt
Role Entry
-------------------- ----- ----- ----- ----- ----- ----- -----
MY_HOST1.MY_COMPANY. Chkd Chkd Chkd Chkd Chkd Chkd Chkd
MY_HOST2.MY_COMPANY. Chkd Chkd Chkd Chkd Chkd Chkd Chkd
-------------------- ----- ----- ----- ----- ----- ----- -----
Legends :
Chkd - Checked. No errors.
Crtd - ASR setup errors were found and corrected.
Err - Error occurred while doing ASR setup verification.
NCrtd - ASR setup has errors, but not corrected.
------------------------------------------------------------------------------
The asrsetup operation is used to create a new Oracle Database Advanced Replication-based directory replication group (DRG). A DRG consists of a master definition site (MDS) and one or more remote master sites (RMS).
Before you begin, stop all Oracle Internet Directory server processes on the MDS and RMS sites. After the setup operation is completed, you can restart all Oracle Internet Directory processes and replication server processes.
Only the optional -v argument is specified on the command-line. The tool will prompt you for the following information.
The database global name of the MDS (as defined in the tnsnames.ora file).
A replication administrator password for the MDS
The SYSTEM password for the MDS
The database global for each RMS (as defined in the tnsnames.ora file).
The SYSTEM password for each RMS
Using the asrsetup operation you can perform the following tasks:
In this example, a DRG is created consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM.
Example:
remtool -asrsetup -v
The results are as follows:
------------------------------------------------------------------------------ ASR Setup for OID Replication WARNING: Make sure that the replication administrator that you enter below does not exist already in any of the nodes that will be part of the DRG to be created now. If the user exists, that user will be dropped and will be created newly. ------------------------------------------------------------------------------ Enter replication administrator's name : repadmin Enter replication administrator's password : Reenter replication administrator's password : Enter Master Definition Site (MDS) details : Enter global name of MDS : MY_HOST1.MY_COMPANY.COM Enter SYSTEM user password of MDS : Enter Remote Master Site (RMS) details : Enter global name of RMS # 1 : MY_HOST2.MY_COMPANY.COM Enter SYSTEM user password of MDS : Are there more Remote Master Sites in the group? [y/n/q] : n Verify the details you had entered. ------------------------------------------------------------------------------ Replication administrator's name : repadmin Master Definition Site : MY_HOST1.MY_COMPANY.COM Remote Master Site # 1 : MY_HOST2.MY_COMPANY.COM Are these details correct? [y/n/q] : y ------------------------------------------------------------------------------ ASR setup in progress... MY_HOST1.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST1.MY_COMPANY.COM : Dropping replication administrator repadmin... MY_HOST1.MY_COMPANY.COM : Creating replication administrator repadmin... MY_HOST1.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST1.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST1.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST1.MY_COMPANY.COM : Creating purge job... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Creating database link to MY_HOST2.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Scheduling push job to MY_HOST2.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST2.MY_COMPANY.COM : Dropping replication administrator repadmin... MY_HOST2.MY_COMPANY.COM : Creating replication administrator repadmin... MY_HOST2.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST2.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST2.MY_COMPANY.COM : Granting privileges or roles required for replication administrator to repadmin... MY_HOST2.MY_COMPANY.COM : Creating purge job... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Creating database link to MY_HOST1.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Scheduling push job to MY_HOST1.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Creating replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Adding object TABLE ODS.ASR_CHG_LOG to replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Generating replication support for TABLE ODS.ASR_CHG_LOG... MY_HOST1.MY_COMPANY.COM : Adding object TABLE ODS.ODS_CHG_STAT to replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Generating replication support for TABLE ODS.ODS_CHG_STAT... MY_HOST2.MY_COMPANY.COM : Dropping replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Adding replication site MY_HOST2.MY_COMPANY.COM to replication group LDAP_REP... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST2.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST2.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST2.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST2.MY_COMPANY.COM : Executing deferred administrative requests... MY_HOST1.MY_COMPANY.COM : Verifying initialization parameter... MY_HOST2.MY_COMPANY.COM : Verifying initialization parameter... MY_HOST1.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST2.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST1.MY_COMPANY.COM : Verifying replication agreement entry... MY_HOST1.MY_COMPANY.COM : Inserting replication agreement entry my_host_... CORRECTED: MY_HOST1.MY_COMPANY.COM : "my_host_rid" hostname has been added to replication agreement entry. MY_HOST1.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid2... CORRECTED: MY_HOST1.MY_COMPANY.COM : "my_host_rid2" hostname has been added to replication agreement entry. MY_HOST2.MY_COMPANY.COM : Verifying replication agreement entry... MY_HOST2.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid... CORRECTED: MY_HOST2.MY_COMPANY.COM : "my_host_rid1" hostname has been added to replication agreement entry. MY_HOST2.MY_COMPANY.COM : Inserting replication agreement entry my_host_rid2... CORRECTED: MY_HOST2.MY_COMPANY.COM : "my_host_rid2" hostname has been added to replication agreement entry. MY_HOST1.MY_COMPANY.COM : Resuming replication activity... ------------------------------------------------------------------------------ ASR setup has been configured successfully. ------------------------------------------------------------------------------ Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ----
This asrverify operation detects and reports on problems found in an Oracle Database Advanced Replication-based directory replication group (DRG). This operation reports errors, but does not correct them. To run this operation, all nodes in the DRG must be up and running. You do not have to stop your Oracle Internet Directory server processes to run this operation.
The asrverify operation will fail or report errors for the following situations. You can use the asrrectify operation to correct these errors. See "The remtool -asrrectify Operation" for more information about that operation.
If, by mistake, the replication administrator account is dropped in any of the nodes, the asrverify operation fails. Use asrrectify to re-create the replication administrator account and add it back to the DRG.
If, by mistake, the password for the replication administrator account has changed on any of the nodes in the DRG, the asrverify operation fails. Use asrrectify to change the replication administrator account and add it back to the DRG.
If the global database name of any node has changed after Advanced Replication setup, asrverify reports an error and does not proceed further. Use asrrectify to revert back to the previous global name and rectify other issues.
remtool -asrverify [-connect repl_admin_name/password@net_service_name] [-v]
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the asrverify operation you can perform the following tasks:
In this example, errors are found in a DRG consisting of two nodes.
Example:
remtool -asrverify -v -conn repadmin/repadmin@my_host1.my_company.com
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS.
MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS.
Directory Replication Group (DRG) details :
--------------------- ----------------------- ------------- ------------- ----
Instance Host Name Global Name Version Replicaid Site
Name Type
--------------------- ----------------------- ------------- ------------- ----
rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS
rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS
-------------------------------------------- ------------- -----------------
----------------------------------------------------------------------------
Verifying ASR setup...
MY_HOST1.MY_COMPANY.COM : Verifying initialization parameter...
MY_HOST2.MY_COMPANY.COM : Verifying initialization parameter...
MY_HOST1.MY_COMPANY.COM : Verifying replication administrator roles...
MY_HOST2.MY_COMPANY.COM : Verifying replication administrator roles...
MY_HOST1.MY_COMPANY.COM : Verifying database links...
MY_HOST2.MY_COMPANY.COM : Verifying database links...
MY_HOST1.MY_COMPANY.COM : Verifying purge job...
MY_HOST2.MY_COMPANY.COM : Verifying purge job...
MY_HOST1.MY_COMPANY.COM : Verifying scheduled links...
MY_HOST2.MY_COMPANY.COM : Verifying scheduled links...
MY_HOST1.MY_COMPANY.COM : Verifying availability of replication objects...
MY_HOST2.MY_COMPANY.COM : Verifying availability of replication objects...
MY_HOST1.MY_COMPANY.COM : Verifying replication group...
ASR SETUP ERROR/WARNING:
MY_HOST1.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ASR_CHG_LOG.
ASR SETUP ERROR/WARNING:
MY_HOST1.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ODS_CHG_STAT.
MY_HOST2.MY_COMPANY.COM : Verifying replication group...
ASR SETUP ERROR/WARNING:
MY_HOST2.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ASR_CHG_LOG.
ASR SETUP ERROR/WARNING:
MY_HOST2.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ODS_CHG_STAT.
MY_HOST1.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry...
MY_HOST2.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry...
MY_HOST1.MY_COMPANY.COM : Verifying replication agreement entry...
MY_HOST2.MY_COMPANY.COM : Verifying replication agreement entry...
-------------------- ----- ----- ----- ----- ----- ----- -----
DB Name Init Repl DB Purge Sch. Repl Repl
Param Admin Links Job Links Group Agrmt
Role Entry
-------------------- ----- ----- ----- ----- ----- ----- -----
MY_HOST1.MY_COMPANY. Chkd Chkd Chkd Chkd Chkd NCrtd Chkd
MY_HOST2.MY_COMPANY. Chkd Chkd Chkd Chkd Chkd NCrtd Chkd
-------------------- ----- ----- ----- ----- ----- ----- -----
Legends :
Chkd - Checked. No errors.
Crtd - ASR setup errors were found and corrected.
Err - Error occurred while doing ASR setup verification.
NCrtd - ASR setup has errors, but not corrected.
------------------------------------------------------------------------------
Summary of findings:
ASR SETUP ERROR/WARNING:
MY_HOST1.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ASR_CHG_LOG.
ASR SETUP ERROR/WARNING:
MY_HOST1.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ODS_CHG_STAT.
ASR SETUP ERROR/WARNING:
MY_HOST2.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ASR_CHG_LOG.
ASR SETUP ERROR/WARNING:
MY_HOST2.MY_COMPANY.COM : Replication support is not available for TABLE ODS.ODS_CHG_STAT.
------------------------------------------------------------------------------
The backupmetadata operation adds the metadata of a pilot replica to the master replica, or backs up the metadata of a pilot replica into a file.
|
Note: The-backupmetadata option will not work if anonymous bind is disabled at the pilot replica or master replica.
|
remtool -backupmetadata -replica pilot_hostname:port/pilot_repldnpwd {-master master_hostname:port/master_replrdnpwd | -bkup file_name}
-replica pilot_hostname:port/pilot_repldnpwd
Required. The connection string for the pilot replica. The string is comprised of the following elements:
The host name where the pilot replica's LDAP server is running.
The pilot replica's LDAP listening port, for example 389.
The password for the replication DN of the pilot replica.
-master master_hostname:port/master_repldnpwd
Either -master or -bkup argument is required. The connection string for the master replica. The string is comprised of the following elements:
The host name where the master replica's LDAP server is running.
The master replica's LDAP listening port, for example 389.
The password for the replication DN of the master replica.
-bkup file_name
Either -master or -bkup argument is required. The full path and file name of the LDIF output file. The metadata entries are written to this file in LDIF format.
Using the backupmetadata operation you can perform the following tasks:
This example shows how to add the metadata entries from a pilot replica to a master replica.
Example:
remtool -backupmetadata -replica mypilot.company.com:389/mypassword -master mymaster.company.com:389/mypassword
The chgpwd operation is used to change the replication administrator password for an Oracle Database Advanced Replication-based directory replication group (DRG) that has already been setup using asrsetup.
The replication administrator password is the same for all nodes in an Advanced Replication DRG. This operation will change the password for all nodes in the DRG.
remtool -chgpwd [-connect repl_admin_name/password@net_service_name] [-v]
The tool will also prompt you to enter the new password for the replication administrator.
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The current password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the chgpwd operation you can perform the following task:
In this example, the password of the replication administrator of a DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM is changed.
Example:
remtool -chgpwd -v -conn repadmin/repadmin@MY_HOST1.MY_COMPANY.COM
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS. MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ---- Enter new password of the replication administrator : Reenter new password of the replication administrator : ------------------------------------------------------------------------------ Changing the password of all nodes... MY_HOST1.MY_COMPANY.COM : Changing password of replication administrator repadmin... MY_HOST2.MY_COMPANY.COM : Changing password of replication administrator repadmin... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Creating database link to MY_HOST2.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Creating database link to MY_HOST1.MY_COMPANY.COM... ------------------------------------------------------------------------------ Password has been changed. ------------------------------------------------------------------------------
The delnode operation removes a remote master site (RMS) node from an existing directory replication group (DRG). You must first create the DRG using "The remtool -asrsetup Operation". The following usage rules apply to this operation:
You can only delete RMS nodes from a DRG, not the master definition site (MDS).
Oracle Internet Directory processes on the master definition site (MDS) and other remote master sites (RMSs) in the DRG must be stopped before running the operation.
If the RMS node being deleted is down when the delnode operation is invoked, it will be selected for deletion.
After the delnode operation is complete, Oracle Internet Directory processes can be restarted.
remtool -delnode [-connect repl_admin_name/password@net_service_name] [-v]
The tool will also prompt you for the global database name (as defined in the tnsnames.ora file of the RMS node to be deleted from the DRG.
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the delnode operation you can perform the following task:
In this example, MY_HOST3.MY_COMPANY.COM is removed from a DRG consisting of MY_HOST1.MY_COMPANY.COM, MY_HOST2.MY_COMPANY.COM and MY_HOST3.MY_COMPANY.COM
Example:
remtool -delnode -v -conn repadmin/repadmin@MY_HOST1.MY_COMPANY.COM
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS. MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. MY_HOST3.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS rid3 my_host MY_HOST3.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid3 RMS -------- ------------- ----------------------- ------------- ------------- ---- Do you want to continue? [y/n] : y Enter globalname of node to be deleted : MY_HOST3.MY_COMPANY.COM ------------------------------------------------------------------------------ Deleting an existing node... MY_HOST1.MY_COMPANY.COM : Dropping replication site MY_HOST3.MY_COMPANY.COM from replication group LDAP_REP... MY_HOST3.MY_COMPANY.COM : Dropping replication group LDAP_REP... MY_HOST3.MY_COMPANY.COM : Unscheduling push job to MY_HOST1.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Unscheduling push job to MY_HOST2.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST1.MY_COMPANY.COM... MY_HOST3.MY_COMPANY.COM : Dropping database link made to MY_HOST2.MY_COMPANY.COM... Enter "SYSTEM" user password for "MY_HOST3.MY_COMPANY.COM" database at "my_host" host : MY_HOST3.MY_COMPANY.COM : Dropping replication administrator repadmin... MY_HOST1.MY_COMPANY.COM : Unscheduling push job to MY_HOST3.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Unscheduling push job to MY_HOST3.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST2.MY_COMPANY.COM : Dropping database link made to MY_HOST3.MY_COMPANY.COM... MY_HOST1.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST2.MY_COMPANY.COM : Verifying uniqueness of replication agreement entry... MY_HOST1.MY_COMPANY.COM : Verifying replication agreement entry... MY_HOST1.MY_COMPANY.COM : Deleting replication agreement entry my_host_rid3... CORRECTED: MY_HOST1.MY_COMPANY.COM : "my_host_rid3" hostname has been removed from replication agreement entry as it is not part of DRG or was repeated. MY_HOST2.MY_COMPANY.COM : Verifying replication agreement entry... MY_HOST2.MY_COMPANY.COM : Deleting replication agreement entry my_host_rid3... CORRECTED: MY_HOST2.MY_COMPANY.COM : "my_host_rid3" hostname has been removed from replication agreement entry as it is not part of DRG or was repeated. ------------------------------------------------------------------------------ Node MY_HOST3.MY_COMPANY.COM has been deleted from this DRG. ------------------------------------------------------------------------------ Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ---- ================================================================================
The dispasrerr operation displays errors for an Oracle Database Advanced Replication-based directory replication group (DRG). It shows both administrative request errors and deferred transaction errors.
remtool -dispasrerr [-connect repl_admin_name/password@net_service_name] [-v]
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the dispasrerr operation you can perform the following task:
In this example, the tool reports Advanced Replication errors for a DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM.
Example:
remtool -dispasrerr -v -conn repadmin/repadmin@my_host1.my_company.com MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS. MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ---- ------------------------------------------------------------------------------ Following administrative request errors were found at MY_HOST1.MY_COMPANY.COM -------------------- -------------------- ------------------------------- Admin request Request raised at Error raised by -------------------- -------------------- ------------------------------- REPADMIN MY_HOST1.MY_COMPANY. ORA-23309: object ODS.ASR_CHG_L REPADMIN MY_HOST1.MY_COMPANY. ORA-23309: object ODS.ODS_CHG_S REPADMIN MY_HOST1.MY_COMPANY. ORA-23416: table "ODS"."ODS_CHG REPADMIN MY_HOST1.MY_COMPANY. ORA-23308: object ODS.ODS_CHG_S REPADMIN MY_HOST1.MY_COMPANY. ORA-23416: table "ODS"."ASR_CHG REPADMIN MY_HOST1.MY_COMPANY. ORA-23308: object ODS.ASR_CHG_L -------------------- -------------------- ------------------------------- ------------------------------------------------------------------------------ Following deferred transaction errors were found at MY_HOST1.MY_COMPANY.COM --------------- --------------- --------------- ---------------------------- Deferred Deferred Trans Destination Error Transaction ID Origin DB --------------- --------------- --------------- ---------------------------- 1.2.3733 MY_HOST1.MY_COM MY_HOST1.MY_COM ORA-01403: no data found --------------- --------------- --------------- ---------------------------- No deferred transaction errors were found at MY_HOST2.MY_COMPANY.COM ------------------------------------------------------------------------------ ------------------------------------------------------------------------------
The dispqstat operation displays the queue statistics for a directory replication group (DRG) that uses Oracle Database Advanced Replication. This operation cannot be used for DRGs that use LDAP-based replication. If a DRG uses both Advanced and LDAP-based replication, this operation displays queue statistics for nodes that use Advanced Replication only.
remtool -dispqstat [-connect repl_admin_name/password@net_service_name] [-v]
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the dispqstat operation you can perform the following tasks:
In this example, queue statistics for an Advanced Replication-based DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM are reported.
Example:
remtool -dispqstat -v -conn repadmin/repadmin@my_host1.my_company.com
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS.
MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS.
Directory Replication Group (DRG) details :
-------- ------------- ----------------------- ------------- ------------- ----
Instance Host Name Global Name Version Replicaid Site
Name Type
-------- ------------- ----------------------- ------------- ------------- ----
rid1 my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS
rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS
-------- ------------- ----------------------- ------------- ------------- ----
Queue Statistics :
-------------- -------------- --------- --------- --------- --------- ---------
Supplier Consumer New Retry Purge HIQ Change #
-------------- -------------- --------- --------- --------- --------- ---------
MY_HOST1.MY CO MY_HOST1.MY CO 3 9 10 6 2003
MY_HOST1.MY CO MY HOST2.MY CO 2 7 8 5 2001
MY_HOST2.MY CO MY_HOST1.MY CO 2 8 5 8 2002
MY_HOST2.MY CO MY_HOST2.MY CO 2 10 7 8 2000
-------------- -------------- --------- --------- --------- --------- ---------
Legends
New: No. of new change logs
Retry: No. of change logs in retry queue
Purge: No. of change logs in purge queue
HIQ: No. of change logs in Human Intervention Queue (HIQ)
Change # : Last applied change log no.
The paddnode operation adds a read-only replica or partial replica to a directory replication group (DRG). This operation has the following usage rules:
The supplier node (the master copy) can be part of a DRG that uses Advanced Replication, LDAP-based replication, or both.
If you want to specify a supplier node that uses Advanced Replication, you must bind using that node's connection information.
The new replica to be added should not be a member of any DRG.
A consumer node (the destination of replication updates) can be any node that uses LDAP-based replication.
After adding a replica, you can choose the naming context(s) to participate in replication, or choose the entire directory by selecting * (asterisk). Choosing specific naming contexts replicates only that portion of the directory. Choosing the entire directory will replicate all directory data except for directory-specific entries (DSE).
The cn=oraclecontext naming context is included for replication whether or not any naming contexts are specified by the user.
The Oracle Internet Directory server at the consumer replica is set to read-only mode.
remtool -paddnode [-bind supplier_hostname:ldap_port/replication_dn_password] [-v]
In addition to the arguments specified on the command-line, the tool will prompt you for the following information:
Consumer Host Name of Host Running OID Server - The host name of the Oracle Internet Directory server where you want to create the read-only replica. This node will be added to the DRG as a read-only replica.
Consumer Port - The LDAP listening port of the consumer node.
Consumer Replication DN Password - The password for the replication DN on the consumer node.
Replica ID of Supplier - If the DRG contains multiple nodes that can be used as the supplier, you will be prompted to enter the replica ID of the one you want to use.
Naming Context - For a partial replica, you can enter the name(s) of the naming context you want to replicate. To select the entire directory, enter * (asterisk). To select none, enter e (end).
-bind supplier_hostname:ldap_port/replication_dn_password
The connection string used to bind to the LDAP directory server of the supplier node. If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The host name of the supplier node.
The LDAP listening port of the supplier node.
The password for the replication DN on the supplier node.
Using the paddnode operation you can perform the following tasks:
In this example, directory server ldap://my_host:3060 is added as a replica to directory server ldap://my_host:3040, which is part of the DRG consisting of ldap://my_host:3040 and ldap://my_host:3080, which both use LDAP-based replication.
Example:
remtool -paddnode -v -bind my_host:3040/ods
The results are:
Directory Replication Group (DRG) details :
--- ------------------ ----------------------- ----------------------- -----
Sl Replicaid Directory Information Supplier Information Repl.
No. Type
--- ------------------ ----------------------- ----------------------- -----
001 my_host_rid1 my_host:3040 -- RW
002 my_host_rid3 my_host:3080 my_host_rid1 RO
--- ------------------ ----------------------- ----------------------- -----
Enter consumer directory details:
Enter hostname of host running OID server : my_host
Enter port on which OID server is listening : 3060
Enter replication dn password :
Enter replicaid of the supplier : my_host_rid1
------------------------------------------------------------------------------
ldap://my_host:3060 [my_host_r[my_host_rid1]id2] : Modifying entry orclreplicaid=my_host_rid2,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Modifying entry ...
ldap://my_host:3040 [my_host_rid1] : Modifying entry orclreplicaid=my_host_rem,cn=replication configuration...
ldap://my_host:3040 [my_host_rid1] : Modifying entry ...
ldap://my_host:3040 [my_host_rid1] : Modifying entry ...
ldap://my_host:3040 [my_host_rid1] : Adding entry orclagreementid=000003,orclreplicaid=my_host_rid,cn=replication configuration...
ldap://my_host:3040 [my_host_rid1] : Adding entry orclreplicaid=my_host_rem2,cn=replication configuration...
ldap://my_host:3040 [my_host_rid1] : Adding entry cn=replication dn,orclreplicaid=my_host_rem2,cn=replication configuration...
ldap://my_host:3080 [my_host_rid3] : Adding entry orclreplicaid=my_host_rem2,cn=replication configuration...
ldap://my_host:3080 [my_host_rid3] : Adding entry cn=replication dn,orclreplicaid=my_host_rem2,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry orclreplicaid=my_host_rem,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry orclagreementid=000002,orclreplicaid=my_host_rem,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry orclagreementid=000003,orclreplicaid=my_host_rid,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry cn=replication dn,orclreplicaid=my_host_rid,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry orclreplicaid=my_host_rem3,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry cn=replication dn,orclreplicaid=my_host_rid3,cn=replication configuration...
ldap://my_host:3080 [my_host_rid3] : Adding entry orclagreementid=000003,orclreplicaid=my_host_rid,cn=replication configuration...
------------------------------------------------------------------------------
Replica ldap://my_host:3060(my_host_rem2) has been added to this DRG.
------------------------------------------------------------------------------
Directory Replication Group (DRG) details :
--- ------------------ ----------------------- ----------------------- -----
Sl Replicaid Directory Information Supplier Information Repl.
No. Type
--- ------------------ ----------------------- ----------------------- -----
001 my_host_rid1 my_host:3040 -- RW
002 my_host_rid2 my_host:3060 my_host_rid1 RO
003 my_host_rid3 my_host:3080 my_host_rid1 RO
--- ------------------ ----------------------- ----------------------- -----
Replica ldap://my_host:3060 (my_host_rid2) can be made partial replica by specifying naming contexts to be replicated.
------------------------------------------------------------------------------
List of available naming contexts in supplier replica ldap://my_host:3040 (my_host_rid1) :
1. * [replicate whole directory]
Enter naming context (e-end, q-quit) : e
------------------------------------------------------------------------------
------------------------------------------------------------------------------
In this example, the directory server ldap://my_host:3060 is added as partial read-only replica by specifying the naming contexts to be replicated to directory server ldap://my_host:3040.
Example:
remtool -paddnode -v -bind my_host:3040/ods
The results are:
Directory Replication Group (DRG) details :
--- ------------------ ----------------------- ----------------------- -----
Sl Replicaid Directory Information Supplier Information Repl.
No. Type
--- ------------------ ----------------------- ----------------------- -----
001 my_host_rid my_host:3040 -- RW
--- ------------------ ----------------------- ----------------------- -----
Enter consumer directory details:
Enter hostname of host running OID server : my_host
Enter port on which OID server is listening : 3060
Enter replication dn password :
------------------------------------------------------------------------------
ldap://my_host:3060 [my_host_rid2] : Modifying entry orclreplicaid=my_host_rid2,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Modifying entry ...
ldap://my_host:3040 [my_host_rid1] : Modifying entry orclreplicaid=my_host_rid1,cn=replication configuration...
ldap://my_host:3040 [my_host_rid1] : Modifying entry ...
ldap://my_host:3040 [my_host_rid1] : Modifying entry ...
ldap://my_host:3040 [my_host_rid1] : Adding entry orclagreementid=000002,orclreplicaid=my_host_rid1,cn=replication configuration...
ldap://my_host:3040 [my_host_rid1] : Adding entry orclreplicaid=my_host_rid2,cn=replication configuration...
ldap://my_host:3040 [my_host_rid1] : Adding entry cn=replication dn,orclreplicaid=my_host_rid2,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry orclreplicaid=my_host_rid1,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry orclagreementid=000002,orclreplicaid=my_host_rid1,cn=replication configuration...
ldap://my_host:3040 [my_host_rid] : Adding entry cn=includednamingcontext000001,orclagreementid=000002,orclreplicaid=usunnae07_prep,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry cn=includednamingcontext000001,orclagreementid=000002,orclreplicaid=usunnae07_prep,cn=replication configuration...
------------------------------------------------------------------------------
Replica ldap://my_host:3060(my_host_rid2) has been added to this DRG.
------------------------------------------------------------------------------
Directory Replication Group (DRG) details :
--- ------------------ ----------------------- ----------------------- -----
Sl Replicaid Directory Information Supplier Information Repl.
No. Type
--- ------------------ ----------------------- ----------------------- -----
001 my_host_rid1 my_host:3040 -- RW
002 my_host_rid2 my_host:3060 my_host_rid1 RO
--- ------------------ ----------------------- ----------------------- -----
Replica ldap://my_host:3060 (my_host_rem2) can be made partial replica by specifying naming contexts to be replicated.
------------------------------------------------------------------------------
List of available naming contexts in supplier replica ldap://my_host:3040 (my_host_rid1) :
1. * [replicate whole directory]
2. dc=com
3. dc=org
4. dc=net
5. dc=edu
Enter naming context (e-end, q-quit) : dc=org
Enter naming context (e-end, q-quit) : dc=edu
Enter naming context (e-end, q-quit) : e
Following naming contexts will be included for replication:
------------------------------------------------------------------------------
1. dc=org
2. dc=edu
Do you want to continue? [y/n] : y
ldap://my_host:3040 [my_host_rid1] : Adding entry cn=includednamingcontext000002,orclagreementid=000002,orclreplicaid=my_host_rid,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry cn=includednamingcontext000002,orclagreementid=000002,orclreplicaid=my_host_rid,cn=replication configuration...
ldap://my_host:3040 [my_host_rid1] : Adding entry cn=includednamingcontext000003,orclagreementid=000002,orclreplicaid=my_host_rid,cn=replication configuration...
ldap://my_host:3060 [my_host_rid2] : Adding entry cn=includednamingcontext000003,orclagreementid=000002,orclreplicaid=my_host_rid,cn=replication configuration...
------------------------------------------------------------------------------
Selected naming contexts have been included for replication.
------------------------------------------------------------------------------
This pchgpwd operation changes the replication DN password for an Oracle Internet Directory server. The password is changed in both the directory and in wallet.
If the replica is taking part in replication, then password will be changed in other replicas for the local replica's replication DN. Note that, unlike Advanced Replication, the replication DN password for each replica can be different.
The operation must be run on the host of the Oracle Internet Directory server whose password you are changing in order to update the wallet password at the same time. You can also update the wallet password separately using "The remtool -pchgwalpwd Operation".
remtool -pchgpwd [-bind oid_hostname:ldap_port/replication_dn_password] [-v]
In addition to the arguments specified on the command-line, the tool will also prompt you for the new replication DN password for the host specified in the bind connection string.
-bind supplier_hostname:ldap_port/replication_dn_password
The connection string used to bind to the Oracle Internet Directory server whose password you want to change. You must run this operation on that host in order to update the wallet password as well. If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The host name of the Oracle Internet Directory server.
The LDAP listening port of the Oracle Internet Directory server.
The current password for the replication DN.
Using the pchgpwd operation you can perform the following tasks:
In this example, the replication DN password of the Oracle Internet Directory server ldap://my_host:3040/ods is changed.
Example:
remtool -pchgpwd -v -bind my_host:3040/ods
The results are:
Directory Replication Group (DRG) details : --- ------------------ ----------------------- ----------------------- ----- Sl Replicaid Directory Information Supplier Information Repl. No. Type --- ------------------ ----------------------- ----------------------- ----- 001 my_host_rid1 my_host:3040 -- RW 002 my_host_rid3 my_host:3080 my_host_rid1 RO --- ------------------ ----------------------- ----------------------- ----- ------------------------------------------------------------------------------ Replication DN password of ldap://my_host:3040 (my_host_rem) associated with database 'rid' will be changed. Do you want to continue? [y/n] : y Enter new password of replication DN : Reenter new password of replication DN : ------------------------------------------------------------------------------ ldap://my_host:3040 [my_host_rid1] : Modifying entry cn=replication dn,orclreplicaid=my_host_rem,cn=replication configuration... ldap://my_host:3080 [my_host_rid3] : Modifying entry cn=replication dn,orclreplicaid=my_host_rem,cn=replication configuration... ------------------------------------------------------------------------------ Password has been changed. ------------------------------------------------------------------------------
The pchgwalpwd operation is used to change the replication DN password only in the wallet of an Oracle Internet Directory server. It sets the wallet password to the same replication DN password stored in the Oracle Internet Directory repository for the host specified in the bind connection string.
remtool -pchgwalpwd [-bind oid_hostname:ldap_port/replication_dn_password] [-v]
-bind supplier_hostname:ldap_port/replication_dn_password
The connection string used to bind to the Oracle Internet Directory server whose wallet password you want to change. If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The host name of the Oracle Internet Directory server.
The LDAP listening port of the Oracle Internet Directory server.
The current password for the replication DN.
Using the pchgwalpwd operation you can perform the following task:
In this example, the replication DN password for Oracle Internet Directory server ldap://my_host:3040 is set in wallet to match the password in the repository.
Example:
remtool -pchgwalpwd -v -bind my_host:3040/ods
The results are:
Directory Replication Group (DRG) details : --- ------------------ ----------------------- ----------------------- ----- Sl Replicaid Directory Information Supplier Information Repl. No. Type --- ------------------ ----------------------- ----------------------- ----- 001 my_host_rid1 my_host:3040 -- RW 002 my_host_rid3 my_host:3080 my_host_rid1 RO --- ------------------ ----------------------- ----------------------- ----- ------------------------------------------------------------------------------ Replication DN password of ldap://my_host:3040 (my_host_rid1) associated with database 'rid' will be set in wallet. Do you want to continue? [y/n] : y
The pcleanup operation is used to clean up an LDAP-based directory replication group (DRG) setup. It will clean up a replica which has incomplete or flawed LDAP-based DRG setup. It will only clean up the replica identified by the bind connection string.
If replication configuration information is corrupted, or the replication DN entry is not available, then the tool will prompt for the Oracle Internet Directory super user DN and password.
This operation only cleans up LDAP-based DRG setup. For clean up of an Oracle Database Advanced Replication-based DRG setup, see "The remtool -asrcleanup Operation".
remtool -pcleanup [-bind oid_hostname:ldap_port/replication_dn_password] [-v]
-bind supplier_hostname:ldap_port/replication_dn_password
The connection string used to bind to the Oracle Internet Directory server whose DRG configuration you want to clean. If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The host name of the Oracle Internet Directory server.
The LDAP listening port of the Oracle Internet Directory server.
The current password for the replication DN.
Using the pcleanup operation you can perform the following tasks:
In this example, the tool cleans up the replication setup of a DRG that has three replicas taking part in LDAP based replication.
Example:
remtool -pcleanup -v -bind my_host:3040/ods
The results are:
Directory Replication Group (DRG) details : --- ------------------ ----------------------- ----------------------- ----- Sl Replicaid Directory Information Supplier Information Repl. No. Type --- ------------------ ----------------------- ----------------------- ----- 001 my_host_rid1 my_host:3040 -- RW 002 my_host_rid3 my_host:3080 my_host_rid1 RO 003 my_host_rid2 my_host:3060 my_host_rid1 RO --- ------------------ ----------------------- ----------------------- ----- DRG identified by replica ldap://my_host:3040 (my_host_rid1) will be cleaned up. Do you want to continue? [y/n] : y ------------------------------------------------------------------------------ ldap://my_host:3040 [my_host_rid1] : Modifying entry orclreplicaid=my_host_rem,cn=replication configuration... ldap://my_host:3040 [my_host_rid1] : Modifying entry ... ldap://my_host:3040 [my_host_rid1] : Modifying entry ... ldap://my_host:3040 [my_host_rid1] : Deleting entry orclagreementid=000002,orclreplicaid=my_host_rem,cn=replication configuration... ldap://my_host:3040 [my_host_rid1] : Deleting entry orclagreementid=000003,orclreplicaid=my_host_rem,cn=replication configuration... ldap://my_host:3040 [my_host_rid1] : Deleting entry orclreplicaid=my_host_rem3,cn=replication configuration... ldap://my_host:3040 [my_host_rid1] : Deleting entry orclreplicaid=my_host_rem2,cn=replication configuration... ldap://my_host:3080 [my_host_rid3] : Modifying entry orclreplicaid=my_host_rem3,cn=replication configuration... ldap://my_host:3080 [my_host_rid3] : Modifying entry ... ldap://my_host:3080 [my_host_rid3] : Modifying entry ... ldap://my_host:3080 [my_host_rid3] : Deleting entry orclreplicaid=my_host_rem,cn=replication configuration... ldap://my_host:3080 [my_host_rid3] : Deleting entry orclreplicaid=my_host_rem2,cn=replication configuration... ldap://my_host:3060 [my_host_rid2] : Modifying entry orclreplicaid=my_host_rem2,cn=replication configuration... ldap://my_host:3060 [my_host_rid2] : Modifying entry ... ldap://my_host:3060 [my_host_rid2] : Modifying entry ... ldap://my_host:3060 [my_host_rid2] : Deleting entry orclreplicaid=my_host_rem3,cn=replication configuration... ldap://my_host:3060 [my_host_rid2] : Deleting entry cn=replication dn,orclreplicaid=my_host_rem3,cn=replication configuration... ------------------------------------------------------------------------------ Replica ldap://my_host:3040(my_host_rid1) has been cleaned up. ------------------------------------------------------------------------------
The pdelnode operation deletes an LDAP-based replica or partial replica from a directory replication group (DRG). To delete an Advanced Replication-based replica, used the "The remtool -delnode Operation".
remtool -pdelnode [-bind hostname:ldap_port/replication_dn_password] [-v]
In addition to the arguments specified on the command-line, the tool will prompt you for the following information:
The replica ID of the replica to be deleted - The replica ID of the LDAP-based replica you want to delete.
-bind hostname:ldap_port/replication_dn_password
The connection string used to bind to the LDAP directory server of an LDAP-based replication node of a DRG. If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The host name of an LDAP-based replica node.
The LDAP listening port.
The password for the replication DN.
Using the pdelnode operation you can perform the following tasks:
In this example, replica ldap://my_host:3080 is removed from the DRG. This DRG consists of three replicas: ldap://my_host:3040, ldap://my_host:3060, and ldap://my_host:3080, of which ldap://my_host:3040 and ldap://my_host:3060 uses Advanced Replication and ldap:my_host:3040 and ldap://my_host:3080 uses LDAP-based replication. To delete replica ldap://my_host:3080, user has to give bind details of either ldap://my_host:3040 or ldap://my_host:3080.
Example:
remtool -pdelnode -v -bind my_host:3040/ods ------------------------------------------------------------------------------ Directory Replication Group (DRG) details : --- ------------------ ----------------------- ----------------------- ----- Sl Replicaid Directory Information Supplier Information Repl. No. Type --- ------------------ ----------------------- ----------------------- ----- 001 my_host_rid1 my_host:3040 my_host_rid2 RW 002 my_host_rid2 -- my_host_rid1 RW 003 my_host_rid3 my_host:3080 my_host_rid1 RO --- ------------------ ----------------------- ----------------------- ----- Enter replicaid of the replica to be deleted : my_host_rid3 ------------------------------------------------------------------------------ ldap://my_host:3040 [my_host_rid1] : Modifying entry ... ldap://my_host:3040 [my_host_rid1] : Deleting entry orclagreementid=000002,orclreplicaid=my_host_rid1,cn=replication configuration... ldap://my_host:3040 [my_host_rid1] : Deleting entry orclreplicaid=my_host_rem3,cn=replication configuration... ldap://my_host:3080 [my_host_rid3] : Modifying entry orclreplicaid=my_host_rem3,cn=replication configuration... ldap://my_host:3080 [my_host_rid3] : Modifying entry ... ldap://my_host:3080 [my_host_rid3] : Deleting entry orclreplicaid=my_host_rem,cn=replication configuration... ------------------------------------------------------------------------------ Replica ldap://my_host:3080(my_host_rid3) has been deleted from this DRG. ------------------------------------------------------------------------------ Directory Replication Group (DRG) details : --- ------------------ ----------------------- ----------------------- ----- Sl Replicaid Directory Information Supplier Information Repl. No. Type --- ------------------ ----------------------- ----------------------- ----- 001 my_host_rid1 my_host:3040 my_host_rid2 RW 002 my_host_rid2 -- my_host_rid1 RW --- ------------------ ----------------------- ----------------------- -----
The pilotreplica operation begins or ends pilot mode for a replica.
remtool -pilotreplica {begin|end} -bind hostname:ldap_port/replication_dn_password [-bkup file_name]
begin | end
Required. Begin or end pilot mode.
-bind hostname:ldap_port/replication_dn_password
Required. The connection string used to bind to the LDAP-based replica for which to begin or end pilot mode. The connect string is composed of three elements:
The host name of an LDAP-based pilot replica.
The LDAP listening port of the pilot replica.
The password for the replication DN.
-bkup file_name
Name of backup file in which entries modified after pilot mode is started are to be stored in LDIF format.
This presetpwd operation resets the replication DN password for the given Oracle Internet Directory server in both the directory repository and wallet. It will not reset the passwords for any other directories of the directory replication group (DRG) of which this directory is a member.
You will need the Oracle Internet Directory super user DN and password to reset the replication DN password.
remtool -presetpwd -bind hostname:ldap_port/replication_dn_password [-v]
In addition to the arguments supplied on the command-line, the tool will prompt you for the following information:
The super user DN, for example cn=orcladmin.
The super user password.
The new replication DN password.
-bind hostname:ldap_port/replication_dn_password
Required. The connection string used to bind to the Oracle Internet Directory server for which to reset the replication DN password. The connect string is composed of three elements:
The host name of the Oracle Internet Directory server.
The LDAP listening port of the Oracle Internet Directory server.
The current password for the replication DN.
Using the presetpwd operation you can perform the following tasks:
In this example, the replication DN password is reset for replica my_host:3040.
Example:
remtool -presetpwdd -v -bind my_host:3040/ods
The results are:
Enter superuser DN : cn=orcladmin Enter superuser password : ------------------------------------------------------------------------------ Replication DN password of ldap://my_host:3040 (my_host_rem) associated with database 'rid1' will be reset. Do you want to continue? [y/n] : y Enter new password of replication DN : Reenter new password of replication DN : ------------------------------------------------------------------------------ ldap://my_host:3040 [my_host_rid1] : Modifying entry cn=replication dn,orclreplicaid=my_host_rid1,cn=replication configuration... ------------------------------------------------------------------------------ Password has been changed. ------------------------------------------------------------------------------
The resumeasr operation resumes replication activity for an Oracle Database Advanced Replication-based directory replication group (DRG) that was previously suspended using the "The remtool -suspendasr Operation".
remtool -resumeasr [-connect repl_admin_name/password@net_service_name] [-v]
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the resumeasr operation you can perform the following tasks:
In this example, replication activity of DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM is resumed.
Example:
remtool -resumeasr -v -conn repadmin/repadmin@MY_HOST1.MY_COMPANY.COM
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS. MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid1 my_host MY_HOST1.MY_COMPANY.COM OID 9.0.4.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 9.0.4.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ---- ------------------------------------------------------------------------------ Altering replication status... MY_HOST1.MY_COMPANY.COM : Resuming replication activity... ------------------------------------------------------------------------------ Replication status has been altered successfully. ------------------------------------------------------------------------------
The suspendasr operation suspends Oracle Database Advanced Replication activity for a directory replication group (DRG) that uses it for replication. While Advanced Replication activity is suspended, replication will not take place.
remtool -suspendasr [-connect repl_admin_name/password@net_service_name] [-v]
-connect repl_admin_name/password@net_service_name
The connection string for the master definition site (MDS) or the Remote Master Site (RMS). If you do not supply the argument on the command-line, the tool will prompt you for the information. The connect string is composed of three elements:
The name of the replication administrator.
The password for the replication administrator.
The net service name of the MDS or RMS. If you have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.
Using the suspendasr operation you can perform the following tasks:
n this example, replication activity of a DRG consisting of MY_HOST1.MY_COMPANY.COM and MY_HOST2.MY_COMPANY.COM is suspended.
Example:
remtool -suspendasr -v -conn repadmin/repadmin@my_host1.my_company.com
The results are:
MY_HOST1.MY_COMPANY.COM is Master Definition Site (MDS). Connected to MDS. MY_HOST2.MY_COMPANY.COM is Remote Master Site (RMS). Connected to RMS. Directory Replication Group (DRG) details : -------- ------------- ----------------------- ------------- ------------- ---- Instance Host Name Global Name Version Replicaid Site Name Type -------- ------------- ----------------------- ------------- ------------- ---- rid my_host MY_HOST1.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid1 MDS rid2 my_host MY_HOST2.MY_COMPANY.COM OID 10.1.2.0.0 my_host_rid2 RMS -------- ------------- ----------------------- ------------- ------------- ---- ------------------------------------------------------------------------------ Altering replication status... MY_HOST1.MY_COMPANY.COM : Quiescing replication activity... ------------------------------------------------------------------------------ Replication status has been altered successfully. ------------------------------------------------------------------------------
