Cloning An Existing Oracle10g Release 2 (10.2.0.x) RDBMS Installation Using OUI [ID 559304.1] by Lucio Teixeira

Page 1 of 4

Cloning An Existing Oracle10g Release 2 (10.2.0.x) RDBMS Installation Using OUI [ID 559304.1] Modified 29-MAY-2009

Type BULLETIN

Status MODERATED

In this Document Purpose Scope and Application Cloning An Existing Oracle10g Release 2 (10.2.0.x) RDBMS Installation Using OUI References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 Oracle Universal Installer - Version: 10.2.0.1 to 10.2.0.4 Information in this document applies to any platform.

Purpose The purpose of this bulletin is to describe how to clone an existing Oracle10g Release 2 (10.2.0.x) RDBMS installation using Oracle Universal Installer (OUI).

Scope and Application This bulletin is intended for anyone who is responsible for installing Oracle software onto a server or cloning an existing Oracle software installation. Please note that Perl 5.6 or higher is required when cloning Oracle10g Release 2 NOTE: When cloning an installation to a new/separate server, it is mandatory to check that the server meets all of the prerequisite requirements. See Note:169706.1 or the Installation Guide for a list of these.

Cloning An Existing Oracle10g Release 2 (10.2.0.x) RDBMS Installation Using OUI Step 1 Install the software you want to clone into the "source" home. For Oracle10g Release 2, install the base software (10.2.0.1 for most platforms) then any required products from the Companion CD and (when available) any required patchsets and/or patches. Please note that you need to install the DB Console so that the required Perl files are installed in $ORACLE_HOME/clone/bin Step 2 Make a copy of the existing (source) Oracle RDBMS installation. If the clone (target) installation is on the same server then the "cp -Rp" command could be used. Before copying the source installation you should shutdown any databases, listeners, agents etc. that are running from the source home (to ensure the integrity of the copy). For example:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BUL...

23/06/2010

Page 2 of 4 cp -Rp /u01/app/oracle/product/10.2.0 /u01/app/oracle/product/10.2.0_clone NOTE: run this command as the 'root' user (the 'p' option will make sure that the ownership of the files is preserved correctly) Alternatively, the source installation could be packed up using the "tar" command: cd /u01/app/oracle/product/10.2.0 tar -cvf /tmp/source.tar . and then moved to the target area (on the same server, or another server) and unpacked: cd /u01/app/oracle/product/10.2.0_clone tar -xvf /tmp/source.tar NOTE: run this command as the 'root' user (to make sure that the ownership of the files is preserved correctly) IMPORTANT NOTES: Before going to step 3, it is important to spend some time checking that the file permissions on files/directories in the target home match those in the source home. Please also check that the validity of any symbolic links has been preserved. Ensure that the links point to files/directories in the new target home, not files/directories in the source home. If necessary, re-create the links. If you are cloning on AIX, make sure that the rootpre.sh script has been executed on the target server. This can be found on the Oracle10g Release 2 media or the script included in patch 6613550 can be executed. If Oracle11g Release 1 is already installed on the target server then rootpre.sh does not need to be executed again. Step 3 Run the following command from the target area to clone the installation with the Oracle Universal Installer (OUI) cd $ORACLE_HOME/clone/bin perl clone.pl ORACLE_HOME="<target_home>" ORACLE_HOME_NAME="<unique_home_name>" If necessary, edit the $ORACLE_HOME/clone/config/cs.properties file to add “–invPtrLoc <path>/oraInst.loc” or “-ignoreSysPrereqs” to the clone_command_line. If clone.pl does not exist, you did not install DB Console (as instructed in step 1). The alternative method of cloning is to use the following commands: cd $ORACLE_HOME/oui/bin ./runInstaller -clone -silent -ignorePreReq ORACLE_HOME="<target_home>" ORACLE_HOME_NAME="<unique_home_name>" If necessary, add "-invPtrLoc <path>/oraInst.loc" or "-ignoreSysPrereqs" to the command line. NOTE: if the home you are trying to clone has products from the Companion CD installed, you must use the ignorePreReq option as a workaround for a known bug. If the server has more than one Perl version installed, it may be necessary to specify the PERL5LIB environment variable so that the versions of the Perl modules match with the Perl version used. NOTE: if you are cloning an Oracle10gR2 Standard Edition installation, please review Note:416255.1 regarding a known issue Note that the full path for the target ORACLE_HOME should be provided (for example, /u01/app/oracle/product/10.2.0_clone)

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BUL...

23/06/2010

Page 3 of 4 Also note that the home name must be unique (that is, it must not already exist in the central inventory file <path>/oraInventory/ContentsXML/inventory.xml). If no central inventory exists on the target server, OUI will create one NOTE: if you are cloning on a server which already has a central inventory and the target home already exists in <path>/oraInventory/ContentsXML/inventory.xml then you should run the following command to 'detach' this home from the central inventory before performing the clone operation: ./runInstaller -detachHome ORACLE_HOME=<target_home> To clone an Oracle10g Release 2 client installation, run OUI directly: ./runInstaller -clone -silent -noconfig ORACLE_HOME="<target_home>" ORACLE_HOME_NAME="<unique_home_name>" Step 4 On Unix/Linux installations, you will now need to run $ORACLE_HOME/root.sh (as root) from the target home Before running root.sh from the target home of a cloned 10.2.0.2 installation on HPUX, please review Note 375213.1 On Unix/Linux platforms, you may (optionally) run $ORACLE_HOME/install/changePerm.sh After cloning 10.2 on HPUX, SQL*Plus (or other applications) may report errors like this: /usr/lib/pa20_64/dld.sl: Mmap failed for the library </u01/app/oracle/product/10.2.0/lib/libsqlplus.sl> : Bad address Please review Note:344772.1 regarding this known issue If you have cloned the installation to a separate server and you want to use the Database Control (dbconsole) application, refer to Note 467598.1 and Note 278100.1 for help with starting the console on the new server. Notes For Windows, use setup.exe (instead of runInstaller) to start OUI Log files are created in the central inventory (<path>/oraInventory/logs) and in the target home ($ORACLE_HOME/clone/logs)

References NOTE:278100.1 - How To Drop, Create And Recreate DB Control In A 10g Database NOTE:300062.1 - How To Clone An Existing RDBMS Installation Using OUI NOTE:344772.1 - /usr/lib/pa20_64/dld.sl: Mmap Failed For The Library `$ORACLE_HOME/lib/libsqlplus.sl` NOTE:375213.1 - After Cloning A 10.2.0.2 Installation, The "root.sh" Script Reports Errors About "fmputl" And "fmputlhp" NOTE:416255.1 - Cloning An Oracle10gR2 Standard Edition Installation Changes It To Enterprise Edition NOTE:467598.1 - The Database Console Fails to Start After a Change in the Hostname NOTE:549268.1 - How To Clone An Existing RDBMS Installation Using EMGC