Replication management tool oracle

When you add an Oracle Database Advanced Replication-based replica, the new replica must be empty. That is, Oracle Internet Directory must be newly installed. The sponsor node for each Oracle Database Advanced Replication-based replica can be any of the following:. In Oracle Internet Directory 11g Release 1, a node cannot be part of more than one multimaster replication group.

The data replicated between servers in a directory replication group does not include DSE root-specific data, server configuration data, and replication agreement data. When an multimaster replication group is configured, the Oracle Single Sign-On database schema is automatically configured in replication. If you want to add a new 10g This section discusses the general tasks you perform when installing and setting up a multimaster replication group. The instructions in this section apply to setting up replication in a group of empty nodes.

They assume that there is no pre-existing directory data on any of the nodes in the DRG. During entry replication, the directory replication server does not always preserve the spaces between RDN components in the DN. In some rare cases, it may not preserve the case of the letters in the DN. You must be able to use Oracle Net Services to connect to the master definition site database and all other nodes in the DRG.

During installation, make sure that each Oracle Internet Directory database instance name is unique on each machine. Install Oracle Internet Directory on the remote master sites in the same way as on the master site. Although Oracle recommends starting with empty replicas, you can set up replication using machines initially configured as masters rather than replicas. To use a machine initially configured as a master as an RMS, you must first migrate its metadata to the MDS, as follows:.

Make sure the Oracle Internet Directory server is up and running on both the MDS and each such desired replica so that the process remtool —backupmetadata can succeed.

If Oracle Delegated Administration Services is not configured, you might see an error message similar to this when you run remtool with the -backupmetadata option:. Apart from loading the metadata into master replica, this tool creates a file named ocbkup. If an error occurs during this operation, remtool reports the error in the terminal from which it was invoked.

The following sections lead you through installing and setting up Advanced Replication by using the Replication Management Tool. To establish a directory replication group DRG , you must configure the Advanced Replication environment by performing the tasks discussed in these topics:. For each node in the directory replication group, perform the steps listed here.

Each step is described more fully in the subsections that directly follow this list. Configure tnsnames. On UNIX, the sqlnet. On Microsoft Windows, the sqlnet. Each tnsnames. For example, if the database global name is mds. You must domain-qualify the net service name for example, sales. Oracle Database Net Services Reference for more information on tnsnames. On UNIX, the tnsnames. On Microsoft Windows, the tnsnames.

To generate online instantiation files, you must use the replication management API. The "Package for Offline Instantiation: Overview" topic in the Replication Management tool online help for detailed information about using the Template Script Generation Wizard to package a deployment template for offline instantiation. The Copy Template Wizard guides you through copying a deployment template. You may need to copy them to multiple master sites for various reasons.

For example, you may want to:. Run the Copy Template Wizard from the master site that contains the deployment template. To open the Copy Template Wizard, right-click the Templates folder in the navigator pane and select Copy. The "Copying a Template" topic in the Replication Management tool online help for detailed information about using the Copy Template Wizard to copy a deployment template. The flowchart in Figure displays the major decisions and tasks that are involved when you create a replication environment using the Replication Management tool.

The flowchart shows the major decisions and steps for building both multimaster and materialized view environments. Each task in the flowchart includes a cross reference to a section in this book that provides more information about the task.

Detailed instructions about completing these tasks are in the Replication Management tool online help. Note: Oracle Enterprise Edition is required for multimaster replication. Note: A replication site can be: A master site only, if it contains master groups but no materialized views. In this case, use the Master Site object to manage the site. A materialized view site only, if it contains materialized views but no master groups.

In this case, use the Materialized View Site object to manage the site. Both a master site and a materialized view site, if it contains both master groups and materialized views. In this case, use both the Master Site object and the Materialized View Site object to manage the site. Note: If you have not created at least one master group, materialized view group, or materialized view at the selected site, the Topology tab displays a message stating that replication must be configured.

Note: The Setup Wizard sets up materialized view sites with untrusted security. See Also: Chapter 2, "Master Replication Concepts and Architecture" for more information about master sites Chapter 3, "Materialized View Concepts and Architecture" for more information about materialized view sites.

See Also: "Materialized View Groups" for more information about materialized view groups. See Also: The "Overview of Creating a Deployment Template" topic in the Replication Management tool online help for detailed information about using the Deployment Template Wizard to create a deployment template.

See Also: Chapter 4, "Deployment Templates Concepts and Architecture" for more information about deployment templates. Note: To generate online instantiation files, you must use the replication management API. See Also: The "Package for Offline Instantiation: Overview" topic in the Replication Management tool online help for detailed information about using the Template Script Generation Wizard to package a deployment template for offline instantiation.

See Also: "Packaging and Instantiation Process" for more information on packaging and instantiating deployment templates. See Also: The "Copying a Template" topic in the Replication Management tool online help for detailed information about using the Copy Template Wizard to copy a deployment template. All Rights Reserved. Oracle9 i Advanced Replication Release 2 9. Book List.

Master Index. See Also: The Replication Management tool online help for detailed instructions about using the Replication Management tool The Oracle Enterprise Manager documentation set and online help for information about using Oracle Enterprise Manager. Text description of the illustration master.

Text description of the illustration adminrequest. Text description of the illustration mastererrors. This section provides examples for tasks that can be performed using the oidcmprec command. The following examples discuss various operations that can be performed with the oidcmprec tool:. The default conflict resolution rules for the compare operation are used. You are prompted for the source directory and destination directory passwords.

It resolves the conflicts that are detected. The default conflict resolution rules for the reconcile operation are used. The scope attribute has been set to subtree. The threads and dnThreads arguments specify the number of worker threads and DN threads. The cmpres file is used to store the report for the operation. The following example compares a directory residing on host1 with another directory residing on host2.

The base argument is set to " " and the scope argument is set to subtree. The following example reconciles a directory residing on myhost1 with another directory residing on myhost2. This example makes use of user-defined values for the -entos , -entod , -atros , -svatrdif , -mvatrdif , and -dndif arguments.

Conflict resolution arguments not specified on the command line, like -atrod , are set to ignore. The merge operation updates both the source and destination directories. The following example performs a compare operation. It uses the exclattr argument to exclude the orclguid , category , userpassword , and authpassword attributes.

The example makes use of wildcard pattern matching to exclude the authpassword attribute subtypes. The following example makes use of the inclattr argument to include the userpassword , cn , sn givenname , and mail attributes. The following example includes all attributes for the compare operation except orclguid , creatorsname , and modifiersname attributes.

This example performs a compare operation on two directories. It overrides the default conflict resolution rules used for the dndif and mvatrdif arguments. The conflict resolution rule for these arguments is set to ignore. The dnThreads argument is specified both in the file and at the command line. The command-line value of dnThreads overrides the value specified in the parameter file.

Substitute the password for password in the example. Because the file contains a password, ensure that it is not readable by unauthorized users.

The following example uses the genchglog argument to ensure that change logs are generated for the operation. When genchglog is set to true , change logs are generated at both the source and destination directories. 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 Oracle Database Advanced Replication-based DRG.

This is the group master. The directory uses change logs to keep track of entries that are being replicated or that are being synchronized by the Oracle Directory Integration and Provisioning. The name of the operation to perform using remtool. See the appropriate operation documentation for command-specific syntax, arguments, and usage.

The following operations are available:. See "The remtool -addnode Operation" for more information about this operation. See "The remtool -asrsetup Operation" for more information about this operation. See "The remtool -chgpwd Operation" for more information about this operation. See "The remtool -delnode Operation" for more information about this operation. See "The remtool -asrcleanup Operation" for more information about this operation.

See "The remtool -asrverify Operation" for more information about this operation. See "The remtool -dispqstat Operation" for more information about this operation. See "The remtool -suspendasr Operation" for more information about this operation. See "The remtool -resumeasr Operation" for more information about this operation.

See "The remtool -dispasrerr Operation" for more information about this operation. See "The remtool -paddnode Operation" for more information about this operation. See "The remtool -pdelnode Operation" for more information about this operation.

See "The remtool -pcleanup Operation" for more information about this operation. See "The remtool -pchgpwd Operation" for more information about this operation.

See "The remtool -pdisplay Operation" for more information about this operation. See "The remtool -pchgmaster Operation" for more information about this operation.

See "The remtool -pchgwalpwd Operation" for more information about this operation. See "The remtool -pdispqstat Operation" for more information about this operation. See "The remtool -pverify Operation" for more information about this operation. See "The remtool -presetpwd Operation" for more information about this operation. See "The remtool -pilotreplica Operation" for more information about this operation.

This operation must be executed at the pilot replica. See "The remtool -backupmetadata Operation" for more information about this operation.

See The remtool -pthput Operation for more information. The connection information to be supplied to remtool. The following connection details are available:. See "The -bind Connection Argument" for more information. See "The -connect Connection Argument" for more information. Runs the command in verbose mode. Shows detailed output for the command on the screen and also logs all operations in the remtool. If there is an existing Oracle Database Advanced Replication-based agreement between two or more nodes, you can convert this agreement to an LDAP multimaster agreement by using the as2ldap operation.

The addnode operation adds a new node to an existing directory replication group DRG. The following usage rules apply to this operation:.

After the addnode operation is complete, Oracle Internet Directory processes can be restarted. The tool also prompts you for the database global name as defined in the tnsnames.

The asrcleanup operation cleans up an existing Oracle Database Advanced Replication-based setup. You must know the system password of all nodes taking part in the directory replication group DRG to run this operation. The tool prompts you to enter the system password for each site. 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 fails if any of the nodes are not running. COM after setting up Advanced Replication. It rectifies this error first before continuing with other checks. 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 prompts you for the following information. 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 fails or report errors for the following situations.

You can use the asrrectify operation to correct these errors. See "The remtool -asrverify 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 remtool 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. 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. The -backupmetadata option does not work if anonymous bind is disabled at the pilot replica or master replica. The connection string for the pilot replica. You are prompted for the password for the replication DN of the pilot replica.

The string is comprised of the following elements:. Either -master or -bkup argument is required. You can provide both arguments. Examples of objects are master groups, materialized view groups, materialized views, materialized view logs, deployment templates, and so on. Right-click a folder or object to create a new object or perform operations on an existing object. Oracle completely redesigned the navigator tree structure in the Replication Management tool in a recent release.

You begin many replication administration operations by selecting the correct object or folder in the navigator tree of the Replication Management tool. The Administration object enables you to manage the entire replication site. Select the Administration object to display the following tabs in the right pane:.

Topology: Displays a graphical view of the replication environment for the selected site. Errors: Displays and lets you manage local errors at the selected site. Transactions: Displays and lets you manage the deferred transactions at the selected site.

Schedule: Displays and lets you manage the push schedules for the database links at the selected site. Also, displays and lets you manage the purge schedule for successfully propagated deferred transactions at the selected site. Configuration: Displays and lets you manage configuration information at the selected site, including initialization parameters important for replication and administrative requests.

Many of these jobs perform important replication functions, such as pushing deferred transactions and purging the deferred transactions queue. If your replication environment is configured for multimaster replication, then you use the Multimaster Replication object to set up your master sites and manage your master groups. The Master Groups folder contains the master groups at the selected site. When you select a master group, you can:. The Materialized View Replication object lets you administer the replication site as it relates to materialized view replication.

You can administer sites that are master sites of materialized view sites, and you can administer materialized view sites themselves. To set up master sites or materialized view sites with the Setup Wizard, right-click the Materialized View Replication object and select Setup Sites. A master site only, if it contains master groups but no materialized views.

In this case, use the Master Site object to manage the site. A materialized view site only, if it contains materialized views but no master groups.

In this case, use the Materialized View Site object to manage the site. Both a master site and a materialized view site, if it contains both master groups and materialized views. In this case, use both the Master Site object and the Materialized View Site object to manage the site. This object lets you manage the master groups at the replication site, and lets you manage sites that are master sites of materialized view sites.

Specifically, this object lets you create, manage, and package deployment templates, and lets you create and manage materialized view logs. Materialized View Logs Folder: This folder lets you create and manage materialized view logs at the master site. To create a new materialized view log, right-click the Materialized View Logs folder and select Create. Templates Folder: This folder lets you create, manage, and package deployment templates at the master site. Right-click the Templates folder and select:.

Create Using Wizard if you want to create a new deployment template with the Deployment Template Wizard. Copy if you want to create a local or remote copy of a deployment template with the Copy Template Wizard. Template Script Generation if you want to package a deployment template for offline instantiation with the Template Script Generation Wizard.

This object lets you manage materialized view sites. Specifically, this object lets you create and manage materialized view groups, materialized views, and refresh groups.

Materialized View Groups Folder: This folder lets you create and manage materialized view groups at the materialized view site. Materialized Views Folder: This folder lets you create and manage individual materialized views at the materialized view site. To create a new materialized view, right-click the Materialized Views folder and select Create. Refresh Groups Folder: This folder lets you create and manage refresh groups at the materialized view site.

To create a new refresh group, right-click the Refresh Groups folder and select Create. The right pane of the Replication Management tool enables you to monitor and manage your replication environment. Figure shows an example of the General tab in the Master Group property sheet.

When you are working with a property sheet, you can click a button that opens a dialog box. For example, if you click the View Administrative Request button on the General property sheet for a master group, then the Administrative Requests dialog box appears, as shown in Figure You can use the right pane of the Replication Management tool to monitor your replication environment. The Topology tab of the Administration property sheet is an example of a monitoring tool that is available to you.

This tab displays a graphical representation of the nodes in your replication environment and the links between them. All of the master sites participating in replication activity for the master groups of the selected site. The total number of the materialized views or materialized view groups connected to the selected master site. The Topology tab only displays values if they are greater than zero. For example, if there are zero administrative requests at a master site, then the number of administrative requests is not displayed.

If you are connected to a replication site that is running Oracle9 i Database or later, then the Topology tab also displays a Statistics button. Click this button to view performance statistics for the replication site. Description of the illustration master.