Use this page to specify the location of the scripts that you may want to execute either before or after Oracle home cloning.
This page is primarily used to customize your cloning operation, and thus is not mandatory. If you do not want to customize the cloning operation, you can leave this page blank, and proceed.
Specify the location of the Pre-Cloning and Post-Cloning scripts that you may want to execute, in the respective fields, and select Execute.
Depending on the type of Oracle home that you are cloning, you may be required to run certain post-install scripts. For more information on various scenarios, see Oracle Home Cloning Use Cases.
Note: The pre-install scripts will be run on the target hosts not on the source hosts.
If you want to execute the scripts as Root, select Use Sudo.
Note: The Use Sudo option is specific to the UNIX environment, and will not be displayed if you are cloning on a Windows platform.
Important: If you do not have Sudo privileges to execute the script as root, you must manually execute root.sh script from the destination clone Oracle home.
See Oracle Home Cloning Use Cases for more information.
Specify the root.sh script location on the destination host. This script will be executed on each destination hosts, at the end of the cloning operation.
If you are cloning to multiple Oracle homes, you can use the %oracle_home%/root.sh place holder instead of entering multiple home locations.
The target properties table provides placeholders that you can use instead of the actual script locations. These placeholders will be instantiated with the appropriate destination locations before the jobs are submitted.
Note:
If you want to execute the root.sh script on the destination hosts, ensure that the user credentials that you have provided for these hosts (in the Destinations page) have sudo privileges.
Important: Although sudo can be used to restrict which commands a user is allowed
to invoke as root (for example, root.sh), for this protection to be foolproof,
the user should not be able to edit any of the files that he is privileged to
execute as root. In this usage case, however, the file root.sh will be owned
by the OS user who owns the Oracle home being installed. The person
performing the clone operation will have access to this OS account.
Therefore, the user performing this operation must be trusted to not abuse the
privilege of running root.sh as root (for example, by
changing its contents to perform undesirable actions), granted through sudo. If the user performing
this operation cannot be trusted in this manner, sudo privileges to run
root.sh should not be granted; rather, a trusted user will need to manually
run root.sh after the clone operation concludes.
Note: After cloning an Oracle Application Server home to a host that is managed by an Oracle Management Agent, the Agent does not automatically discover the targets in the cloned home. To manually discover the new home, go to Grid Control Discovery, and use AS Control configure central management.
Related Topics
Cloning Database Clusters (RAC)
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved