Cloning an Oracle home involves creating a copy of the Oracle home and then configuring it for a new environment. If you are performing multiple Oracle Database installations, then you may want to use this method to create each Oracle home, because copying files from an existing Oracle Database installation takes less time than creating a new version of them. This method is also useful if the Oracle home that you are cloning has had patches applied to it. When you clone this Oracle home, the new Oracle home will have the patch updates as well.
When cloning Database Oracle homes using 11.1 Database Control, you need to update the exclude file list. This file list specifies files that need not be included when the source Oracle home is archived because these files are not required for the clone operation. The following files should not be included in the archive:
Note:In addition to cloning an Oracle home, you can clone individual Oracle Database installations by using Enterprise Manager Database Control. Oracle Database Administrator's Guide provides detailed information about cloning Oracle Database installations and Oracle homes.
To clone an Oracle home:
Verify that the installation of Oracle Database that you want to clone has been successful.
You can do this by reviewing the
.log file for the installation session, which is normally located in the
If you have installed patches, then you can check their status using the following:
$ cd $ORACLE_HOME/OPatch
$ opatch lsinventory
Stop all processes related to the Oracle home. Refer to "Removing Oracle Software" section for more information on stopping the processes for an Oracle home.
Create a ZIP file with the Oracle home (but not Oracle base) directory.
For example, if the source Oracle installation is in the
/u01/app/oracle/product/11.1.0/db_1, then you zip the
db_1 directory by using the following command:
# zip -r db_1.zip /u01/app/oracle/product/11.1.0/db_1
Leave out the
oradata directories that are in the
11.1.0 directory. These directories will be created in the target installation later, when you create a new database there.
# unzip -d / db_1.zip
On the target computer, change directory to the unzipped Oracle home directory, and remove all the .ora (*.ora) files present in the unzipped
$ORACLE_HOME/oui/bin directory, run Oracle Universal Installer in clone mode for the unzipped Oracle home. Use the following syntax:
$ORACLE_HOME/oui/bin/runInstaller -silent -clone ORACLE_BASE="target_oracle_base" ORACLE_HOME="target_oracle_home" ORACLE_HOME_NAME="unique_name_on node" [-responseFile full_directory_path]
$ORACLE_HOME/oui/bin/runInstaller -silent -clone ORACLE_BASE= "/u01/app/oracle/" ORACLE_HOME="/u01/app/oracle/product/11.1.0/db_1" ORACLE_HOME_NAME="db_1"
-responseFile parameter is optional. You can supply clone-time parameters on the command line or by using the response file named on the command line.
Oracle Universal Installer starts, and then records the cloning actions in the
.log file. This log file is normally located in
To configure connection information for the new database, run Net Configuration Assistant.
$ cd $ORACLE_HOME/bin $ ./netca
To create a new database for the newly cloned Oracle home, run Database Configuration Assistant as follows:
$ cd $ORACLE_HOME/bin $ ./dbca
Oracle Universal Installer and OPatch User's Guide for detailed information about using Oracle Universal Installer to clone an Oracle Database home
Oracle Database Administrator's Guide for information about cloning an Oracle databases, and cloning an Oracle Database home
Use the following steps to configure Oracle Configuration Manager for a cloned Oracle home:
emSnapshotEnv script from
bin directory as follows:
Copy the content of the
pending directory as follows:
cp ccr/inventory/core.jar $ORACLE_HOME/ccr/inventory/pending
Use the following command to remove the previous state files:
If you have removed the state files, then you must relink the core functions with the following command:
Use the following command to rerun Oracle Configuration Manager: