Rapid Cloning (Oracle Apps 11i and R12)

Cloning is the process of creating an identical copy of an already existing Oracle Applications system. The new system including component versions, operating system, and platform type must be initially identical to the existing system. Rapid Clone is the new cloning utility introduced in Release 11.5.8. Rapid Clone leverages the new installation and configuration technology utilized by Rapid Install. See Oracle MetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone) for instructions on installing and enabling Rapid Clone, pre-requisite patches etc. You may want to clone an Applications system for several reasons. * Creating a test system from a recent copy of the production system in order to test patches against before applying to production. * Periodically refreshing a test system from a production system in order to keep the test system current. * Moving an existing system to a different machine. In this document, I have tried to explain the rapid cloning process with 11i as well as R12 Technology. We can do cloning using cold as well as hot backup of database. Here I have used cold backup method for cloning. Use the following steps for Rapid cloning Steps Description

Steps on Source Step1 Run the adpreclone.pl file on DBTier and APPSTier of Source DBTier : Execute following command from $ORACLE_HOME/appsutil/scripts perl adpreclone.pl dbTier It will ask for apps password, enter the apps password

APPSTier : Execute following command from $COMMON_TOP/admin/scripts perl adpreclone.pl appsTier It will ask for apps password, enter the apps password Step2 Take Source Application Down (From all the application nodes if you have multiple application nodes) Execute adstpall.sh script from $COMMON_TOP/admin/scripts/ ( For R12 $INST_TOP/apps/$CONTEXT_NAME/admin/scripts ) Step3 Take Source Database listener and database Down Execute following script from $ORACLE_HOME/appsutil/scripts/ ( For R12 $ORACLE_HOME/appsutil/scripts ) addlnctl.sh stop <SID> addbctl.sh stop immediate Step 4 Copy All the TOP Folders from Source to target (You can perform this copying process by making tar files of below folders also. To make tar, use command: tar -cvf <path>/foldername.tar <foldername> ) For 11i Database DB_TOP DATA_TOP For R12 Database Apps_ST Tech_ST Apps_ST Tech_ST INST_TOP

APPL_TOP ApplicationCOMMON_TOP ORA_TOP

Application

Step5 Take Source Database and its listener Up Execute script from $ORACLE_HOME/appsutil/scripts/ ( For R12 $ORACLE_HOME/appsutil/scripts )

addbctl.sh start addlnctl.sh start <SID>

Step6 Take Source Application UP ( from all the application nodes if you have multiple application node) Execute adstrtal.sh script from $COMMON_TOP/admin/scripts/ ( For R12 $INST_TOP/apps/$CONTEXT_NAME/admin/scripts ) Step7 Submit the Active Users request and check its output for confirmation

Steps on Target
Steps Description Step 1 if you have a tar files then untar it. To untar use command : go to the location where you want to untar and give the comand : untar -xvf <path>/tarfilename.tar Step2 Change the owner and file permissions of copied Folders on Target ( If Required ) Run Post Cloning Steps on DBTier cd $HOME vi .profile comment any env file sourced. Logout and login to server and execute following command $echo $ORACLE_HOME It should not display output.

Enter following commands, export PERL5LIB=<RDBMS ORACLE_HOME>/Apache/perl/lib/5.00503 export PATH=<RDBMS ORACLE_HOME>/Apache/perl/bin:$PATH cd <RDBMS ORACLE_HOME>/appsutil/clone/bin Note down the following path Database Node Name RDBMS ORACLE HOME utl_file All DATA TOP DISPLAY PORT Number Execute following command from $<RDBMS ORACLE_HOME>/appsutil/clone/bin perl adcfgclone.pl dbTier Provide the values required for creation of the new Database Context file like, Enter the APPS password [APPS]: Do you want to use a virtual hostname for the target node (y/n) [n] ?: Target instance is a Real Application Cluster (RAC) instance (y/n) [n]: Target System database name [PROD]: Target system RDBMS ORACLE_HOME directory Target system utl_file accessible directories list Number of DATA_TOPs on the target system [3]: Do you want to preserve the Display set to oraproddb1:1.0 (y/n) [y] ?: Do you want to preserve the port values from the source system on the target system (y/n) [y] ?:

Enter the port pool number [0-99]: Monitor the log file during process Step3 Run Post Cloning Steps on appsTier (If you have a multiple application tiers then perform below steps on multiple nodes starting from Concurrent node) cd $HOME vi .profile comment any env file sourced. Logout and login to server and execute following command $echo $ORACLE_HOME It should not display output. Enter following commands, export PATH=<ORA_TOP>/iAS/Apache/perl/bin:$PATH export PERL5LIB=<ORA_TOP>/iAS/Apache/perl/lib/5.00503 cd <COMMON_TOP>/clone/bin Note down the following path Database Node Name APPL_TOP COMMON_TOP 8.0.6 ORACLE HOME iAS ORACLE HOME RDBMS ORACLE HOME utl_file DISPLAY (for R12

PORT Number Execute following command from $COMMON_TOP/clone/bin perl adcfgclone.pl appsTier Provide the values required for creation of the new APPL_TOP Context file Enter the APPS password [APPS]: Do you want to use a virtual hostname for the target node (y/n) [n] ?: Target system database SID : Target system database server node : Target system database domain name Does the target system have more than one application tier server node(y/n) [y] ? Does the target system application tier utilize multiple domain names (y/n)[n] ? Target system concurrent processing node Target system administration node Target system forms server node Target system web server node Is the target system APPL_TOP divided into multiple mount points (y/n)[n] ?: Target system APPL_TOP mount point Target system COMMON_TOP directory Target system 8.0.6 ORACLE_HOME directory Target system iAS ORACLE_HOME directory Do you want to preserve the Display set to Do you want to preserve the port values from the source system on the target system (y/n)[y] Enter the port pool number [0-99]:

UTL_FILE_DIR on database tier consists of the following directories Monitor the log file during process Step4 Perform Post Cloning Tasks as per requirement like Site name (%site%) Web address (%web%) Help Link (help%) Current common_top Update workflow entries change sysadmin password change color (java color) change apps password Make the necessary changes in custom scripts, user level profiles etc. (Please check FNDCPASS Utility page in same blog for How to change apps password ) Update as follows: select TEXT_VALUE from WF_NOTIFICATION_ATTRIBUTES where TEXT_VALUE like %<SID>%<Port Number>% update WF_NOTIFICATION_ATTRIBUTES set TEXT_VALUE = NULL where TEXT_VALUE like %<SID>%<Port Number>% select TEXT_VALUE from WF_ITEM_ATTRIBUTE_VALUES where TEXT_VALUE like %<SID>%<Port Number>% update WF_ITEM_ATTRIBUTE_VALUES set TEXT_VALUE = NULL where TEXT_VALUE like %<SID>%<Port Number>% select GUID from WF_SYSTEMS

Ensure GUID is different of source and target. select NAME from WF_SYSTEMS Ensure NAME is different of source and target. select ADDRESS from WF_AGENTS Ensure ADDRESS is different of source and target. select LOGFILE_NAME from FND_CONCURRENT_REQUESTS update FND_CONCURRENT_REQUESTS set LOGFILE_NAME = NULL where LOGFILE_NAME like %<SID>% select OUTFILE_NAME from FND_CONCURRENT_REQUESTS Step5 Take Application Down ( from all the application nodes if you have multiple application node) Execute adstpall.sh script from $COMMON_TOP/admin/scripts/ ( For R12 $INST_TOP/apps/$CONTEXT_NAME/admin/scripts ) Step6 Clean the FND Node On SQL prompt as apps user run following commands EXEC FND_CONC_CLONE.SETUP_CLEAN; COMMIT; EXIT; Step7 Execute autoconfig.sh on dbTier from $ORACLE_HOME/appsutil/scripts Step8 Execute autoconfig.sh on appsTier $COMMON_TOP/admin/scripts (For R12 $INST_TOP/apps/$CONTEXT_NAME/admin/scripts) Step9 Start the Application ( from all the application nodes if you have multiple application node start from concurrent node) Execute adstrtal.sh script from $COMMON_TOP/admin/scripts/

( For R12 $INST_TOP/apps/$CONTEXT_NAME/admin/scripts ) Step10 Submit the Active Users request and check its output for confirmation

FAQs
1. What is cloning? Cloning is the process of creating an identical copy of an already existing Oracle Applications system. 2. How can I clone an Oracle Applications system?

There are two cloning methods documented in the following white papers available off of Oracle MetaLink Note 135792.1 3. What is the AD Cloning utility?

AD Cloning utility (adclone.pl) is the name of the cloning command line utility. This utility is used to preserve and apply configuration information to the cloned target system. 4. What is Rapid Clone?

Rapid Clone is the new cloning utility introduced in Release 11.5.8. Rapid Clone leverages the new installation and configuration technology utilized by Rapid Install. See OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone) for instructions on installing and enabling Rapid Clone. 5. How do I determine if my system is Rapid Clone enabled?

First, verify that your system is AutoConfig enabled. Then, verify that you have applied the latest Rapid Clone patch documented in OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone). See Searching the Patch History Database in the AD Procedures Guide for instructions on searching for patches applied to your system. There are several identifiers for when the system is AutoConfig enabled. The following are two common indicators: Open the environment file APPSORA.env in your APPL_TOP. If the top of the file says that it is maintained by AutoConfig, then your system is probably using AutoConfig. Check if there is an Applications Context file in the APPL_TOP/admin directory. This file will typically be named <SID>.xml or <SID>_<HOSTNAME>.xml. Check if there is an Applications Context file in the RDBMS ORACLE_HOME under the appsutil directory. This file will typically be named <SID>.xml or <SID>_<HOSTNAME>.xml.

6.

What is AutoConfig?

AutoConfig is a configuration tool that supports automated configuration of an Oracle Applications Instance. All of the information required for configuring an Applications instance is collected into a central repository, called the Applications Context. When the AutoConfig tool runs, it uses information from the Applications Context file to generate configuration files and update database profiles. See OracleMetaLink Note 165195.1 for details on installing and migrating to AutoConfig. 7. We are running Release 11.5.8 (or any later release), which cloning

method can we use? In 11.5.8 AutoConfig is enabled on the middle tier out of the box. In 11.5.9 and any later release, AutoConfig is enabled by default on both the database tier and the middle tier. Update AutoConfig and Rapid Clone code to the latest code line and use Rapid Clone to clone your system. Full instructions are in Cloning Oracle Applications Release 11i with Rapid Clone document 230672.1 on OracleMetalink. 8. Can I clone from one operating system version to another?

Yes, if the target system platform is binary compatible with the source system platform. For example, if you have an existing single-node Oracle Applications system on Solaris 2.6, you could clone it to a node running Solaris 8, but not to a node running HP-UX. Note that cloning from a higher version of a platform to a lower version is not supported, for example, from Solaris 8 to Solaris 2.6. Other examples of binary compatibility for Oracle Applications are: AIX 4.3.3 to AIX 5.1 (32-bit) HP-UX 11.0 to HP-UX 11i Windows NT to Windows 2000 Within a same platform you can also clone from a 32bit source system to a 64bit target system. Note (AIX only): when cloning from AIX 32bit to AIX 64bit, apply patch 2896876 (64bit kernel extension for Oracle) on the target system prior to running adcfgclone.pl. 9. Can I clone a single-node system to a multi-node system?

The Rapid Clone cloning method allows for cloning a single-node system to a multi-node system. See the Cloning Oracle Applications Release 11i with Rapid Clone white paper for details. 10. Can I clone a multi-node system to a single-node system?

You can use Rapid Clone to merge multiple APPL_TOP and COMMON_TOP file systems into a single APPL_TOP and COMMON_TOP file system. For more details about this procedure, see Section 3: Merging existing APPL_TOPs into a shared APPL_TOP in document 233428.1 on OracleMetaLink. 11. What is context file?

Context file is a central repository, which stores all application configuration information. The name is like <Instance name>_ <Server name>.xml 12. How autoconfig will create env and configuration files?

Autoconfig will go to each and every top template directory take the templates from there and fill the values from xml file and create the required files. 13. In how many phases autoconfig will run?

Autoconfig will run in 3 phases. 1. INIT Instantiate the drivers and templates 2. SETUP Fill the template with values from xml and create files 3. PROFILE Update the profile values in database. 14. What is the location of adconfig log file?

APPL_TOP/admin/<context_name>/log/<timestamp directory>