Clone Oracle Home: Destinations Page

Use this page to specify the destination host and Oracle home for the new clone.

On the Destinations page, specify:

The destination host or hosts to which you want to clone the selected Oracle home.
The destination Oracle home directory location.
The destination Oracle home name.
The host (operating system) credentials. This user must have privileges to read and write files on the destination host.

Note: If you are cloning an Oracle Custerware home, ensure the user name is identical in each host.

A working directory on each destination host to use for temporary files that are staged as part of the cloning operation. This working directory is required at both source and destination to help you perform a space estimate.

Important:

Do not specify the Oracle home location or the working directory location within quotes (for example, /scratch/pjohn/emgc/'102_ias_home'). If you specify these locations within quotes, the system may hang.
When specifying the Oracle home location or the working directory location, you must specify four backslashes instead of the usual two (for example, if the location is \\<hostname>\<Oracle home>, you must specify this as \\\\<hostname>\Oracle home>). This is required because the Oracle home cloning job uses the perl script in a manner that causes double backslashes to be converted into a single backslash, thus causing a syntax error.
If you are cloning Oracle software on the same host as the reference installation, then ensure that the destination Oracle home location is not under the source Oracle home location. For example, if the source home is <source_home_location> then the destination Oracle home cannot be of type <source_home_location>/destination_home.
When cloning, ensure that the locale of the source and destination Oracle homes is the same.

Usage Tips

The user whose host (operating system) credentials you specify must also have write access to the central Oracle Universal Installer inventory on the destination host. You can clone an Oracle home to only one new Oracle home per host.

You must run the root.sh script on the destination host after the clone job is completed, for Enterprise Manager to properly configure the cloned Oracle homes. This is required only on non-Windows platforms.

You can automate this task by specifying the root.sh script location, on the Pre/Post Scripts page, and selecting Execute. The Cloning application will automatically execute root.sh on each destination host, at the end of the cloning operation.

Related Topics

About Cloning

Cloning an Oracle Home

Cloning a Database

Oracle Home Cloning Use Cases

Enterprise Manager Information Roadmap