Use this page to specify the required source setting parameters for the Oracle home cloning operation. The options that are displayed on this page vary, based on the source Oracle home type (Installed Oracle Home, or Software Library) that you have selected in the Source Home page.
If you have selected an Oracle home from the Software Library, this home will already be archived and stored in the software library and hence, a working directory to stage all the clone files is not required. Such Oracle home types also do not require any file exclusions to be specified. The only parameter that you may have to specify is to determine whether to treat the source home as a cluster or not.
If the source Oracle home is of an installed Oracle home type, you must specify the following parameters.
This section will be displayed only when you are performing RAC (version 10.1 or 10.2) or a 10g R2 (10.2) Oracle Clusterware cloning operation. Here, you can determine whether the source instance that you want to clone must be treated as a Cluster or not.
If the source database instance is part of a cluster by default, Enterprise Manager displays all the existing nodes of that source cluster.
You can select Source Home is Clustered, to treat the source database instance as a RAC.
Note: If you select this check box, you will be taken to the Product Settings page. If you do not make this selection, you will be directed to the Destination page.
Enter a working directory location on the source host. This location is required to stage the files for cloning.
Note: Ensure that you specify an existing directory location. For example, /tmp on a Linux machine, and c:\temp on a Windows machine. This working directory is required at both source
and destination to help you perform a space estimate.
If there are files in the Oracle home that you do not want to archive, provide a list of these file names or file extensions. Use of wild cards is permitted. Use commas to separate items in the list.
By default, files with the .log and .dbf extension are excluded from a database clone operation.
Note: Since the .log files may be required during Application Server cloning, it is recommended that you do not exclude these files from the cloning operation.
In the Host Credentials section, specify the host (operating system) credentials of a user with read/write permissions at the source Oracle home.
If the currently logged user had supplied the credentials during a previous cloning operation, the Cloning application will automatically pick up those credentials and populate the respective fields.
Enterprise Manager will use these credentials to access the source Oracle home on the destination host through the Agent.
Related Topics
Cloning Database Clusters (RAC)
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.