Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.

1] Modified 03-JAN-2011 PUBLISHED Last Updated: January 3, 2011 This knowledge document describes the process of cloning an Oracle Applications Release 12 system. The content applies to all Release 12.x.x versions, such as 12.0, 12.0.4, and 12.1.x. Where applicable, 12.0.x releases will in general be referred to as Release 12.0, and 12.1.x releases as Release 12.1. The most current version of this document can be obtained in Oracle Support Knowledge Document 406982.1. There is a change log at the end of this document. In This Document
• • • •

Type BULLETIN

Status

Cloning Oracle Applications Release 12 with Rapid Clone

Section 1: Prerequisite Tasks Section 2: Cloning Tasks Section 3: Finishing Tasks Section 4: Advanced Cloning Options

Terminology Cloning is the process used to create a copy of an existing Oracle Applications system. There are various scenarios for cloning an Oracle Applications system, including:
• • •

Standard cloning - Making a copy of an existing Oracle Applications system, for example a copy of a production system to test updates. System scale-up - Adding new machines to an Oracle Applications system to provide the capacity for processing an increased workload. System transformations - Altering system data or file systems, including actions such as platform migration, data scrambling, and provisioning of high availability architectures. Patching and upgrading - Delivering new versions of Applications components, and providing a mechanism for creating rolling environments to minimize downtime.

An important principle in Oracle Applications cloning is that the system is cloned, rather than the topology. Producing an exact copy of the patch level and data is much more important than creating an exact copy of the topology, as a cloned system must be able to provide the same output to the end user as the source system. However, while a cloned system need not have the full topology of its source, it must have available to it all the topology components that are available to the source.

and on the Oracle Applications Installation and Upgrade Notes for each Platform.1. ensure the target system meets all the requirements for Oracle Applications Release 12 stated on the Oracle Applications Release Notes. Note: On Microsoft Windows. CONTEXT_NAME is [SID]_[HOSTNAME]. prepare the source system by applying any required patches and running AutoConfig. If using files bigger than 2Gb. 2. Verify OS requirements on target system Before cloning to a new server. User that owns the database tier file system (RDBMS ORACLE_HOME and database files). All source 2. Section 1: Prerequisite Tasks Before cloning. Oracle Applications system being created as a copy of the source. Text enclosed in brackets represents a variable. Table 1: Software Requirements Software Component Zip Minimum Version Required Location Comments Download from InfoZip. The CONTEXT_NAME variable refers to the name of the CONTEXT_NAME Applications context file. For the latest installation guidelines refer to My Oracle Support Knowledge Document 405565.3 system (or higher) nodes . Zip must be in your $PATH. The 'Location' column indicates the node where the software component must reside. Rapid Clone is not currently certified for use from Domain User Accounts. you should use InfoZip ZIP 3. Monospace Text [] Represents command line text. Verify source and target system software components and versions In addition to the Oracle Applications software requirements (see Oracle Applications Installation Guide: Using Rapid Install).Conventions used in this document include the following: Term or Usage Source system Target system APPLMGR ORACLE Meaning or Action Oracle Applications system being cloned. Substitute a value for the variable text. Type this command exactly as shown. the following software component versions must exist on the source or target nodes as applicable. By default. 1. User that owns the application tier file system (APPL_TOP and application tier technology stack).0 or higher. Do not type the brackets.

b.B.DELTA.1. For example. versions for earlier releases are also available from the Oracle E-Business Suite Online Documentation Library 3.3 and Database 10g. Refer to Oracle Applications Installation Guide: Using Rapid Install (see Footnote 1) Use the Perl shipped with OracleAS 10. Table 2.x All target system nodes Footnote 1 This is the Release 12. ld.AD.3 Description R12. Operating N/A system utilities All target system nodes Perl 5.pl. Table 2.Unzip All source 5. Perl must be in your $PATH. At the time of writing this note.0 AD patches Patch 6510214 For Release 12.52 system (or higher) nodes Download from InfoZip. .A.1.4 4.1: Apply patches as listed in Table 2. make. you should use InfoZip UNZIP 5. Unzip must be in your $PATH.DELTA. or download it from Perl.a: Release 12.52 or higher.a. Refer to My Oracle Support Knowledge Document 387859.1 version.com. Apply the latest AutoConfig template patch Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes.b: Release 12. and $PERL5LIB must be set correctly before cloning. Apply the latest AD patch Refer to My Oracle Support to obtain the latest AD patch. The required operating system utilities for your platform must be in your $PATH when running adcfgclone.0: Apply patches as listed in Table 2. If using files bigger than 2Gb.AD. and ar on UNIX. the following patches were available: For Release 12.1 AD patches Patch 9239089 Description R12.1 for details of the latest AutoConfig Template rollup patch.

Table 3. Table 3. Run AutoConfig on the application tiers Follow the steps under section " Run AutoConfig on the Application Tiers " in My Oracle Support Knowledge Document 387859.0 Rapid Clone patches Patch 5484000 9171651:R12.B Description 12.1 Rapid Clone patches Patch 9171651:R12.c: Other Patches Patch 8246709 Description Required for Microsoft Windows if using OracleAS 10. 6.a.A 9833058:R12.5. Apply the latest Rapid Clone patches Update the Oracle Applications file system with the latest Rapid Clone files by applying the following patches to all Applications nodes.0.4 ORACLE_HOME before every cloning opera Note: If new Rapid Clone or AutoConfig updates are applied to the system.0: Apply patches as listed in Table 3. This patch must b applied to the OracleAS 10.OAM.a: Release 12. 7.OAM.B 9833058:R12.3.OAM.OAM.1: Apply patches as listed in Table 3.1 to run AutoConfig on all application tier nodes. and 8 below must be executed again in order to apply the new files to the database node.3.0 RAPIDCLONE CONSOLIDATED FIXES JUL/2010 HOT CLONE FAILS WITH ORA-00201 DURING RECOVERY MA ○ For Release 12.2 Release Update Pack (RUP2) or 12.1.b: Release 12. steps 6.4.c. ○ For Release 12.b.1. .1 RAPIDCLONE CONSOLIDATED FIXES JUL/2010 HOT CLONE FAILS WITH ORA-00201 DURING RECOVERY ○ Other Patches (All releases): Apply patches as listed in Table 3. Table 3.A Description Oracle E-Business Suite 12.

Log in to each application tier node as the APPLMGR user.pl dbTier b. Follow the steps under section "Run AutoConfig on the Database Tier" in My Oracle Support Knowledge Document 387859. and run the following commands: $ cd [RDBMS ORACLE_HOME]/appsutil/scripts/ [CONTEXT_NAME] $ perl adpreclone. Run AutoConfig on the database tier 9. . 1.pl utility. each of which is made up of several logical sections and their steps. 8. Prepare the source system database tier for cloning Log on to the source system as the ORACLE user.1 to copy AutoConfig and Rapid Clone files to each database node via the admkappsutil.1 to run AutoConfig on the database tier nodes. versions for earlier releases are also available from the Oracle E-Business Suite Online Documentation Library).pl appsTier Note: If new Rapid Clone or AutoConfig updates are applied to the system. and run the following commands on each node that contains an APPL_TOP: $ cd [INST_TOP]/admin/scripts $ perl adpreclone. Refer to Oracle Applications Maintenance Utilities for more information (this is the Release 12. Note: Rapid Clone never changes the source system configuration. adpreclone.pl must be executed again on the dbTier and on the appsTier in order to apply the new files into the clone directory structures that will be used during the cloning configuration stage. The cloning process consists of three phases. Prepare the source system application tier for cloning Log on to the source system as the APPLMGR user.1 version. Synchronize appsutil on the database tier nodes Follow the steps under section "Copy AutoConfig to the RDBMS ORACLE_HOME" in My Oracle Support Knowledge Document 387859. After the source system is copied to the target. Rapid Clone updates these templates to contain the new target system configuration settings. Prepare the source system Execute the following commands to prepare the source system for cloning: a.7. Maintain snapshot information Section 2: Cloning Tasks Use Rapid Clone to create template files for cloning on the source system. and run "Maintain Snapshot information" in AD Administration.

nmb. Copy the source database ORACLE_HOME to the target system 4.e. etc). Additionally. UNIX/Linux users should ensure that the symbolic links (soft links) are preserved when copying. and then: 1. nmhs. Copy the source system to the target system Copy the application tier file system from the source Applications system to the target node by executing the following steps in the order listed.2. a. nmo.dbf) files from the source system to the target system 3. you may require the -h option to follow symbolic links. Start the source Applications system database and application tier processes . If you use this command. this can be accomplished with the cp -RH command. Copy the application tier file system Log on to the source system application tier nodes as the APPLMGR user and shut down the application tier server processes. Consult the UNIX man page for the tar command. Copy the database node file system Log on to the source system database node as the ORACLE user. Note: In the copying tasks below. Perform a normal shutdown of the source system database 2. Consult the UNIX man page for the cp command to check the parameters available on your platform. verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root (i. Copy the following application tier directories from the source node to the target application tier node: • • • [APPL_TOP] [COMMON_TOP] Applications Technology Stack:  [OracleAS Tools ORACLE_HOME]  [OracleAS Web IAS_ORACLE_HOME] b. the tar command can be used to compress the directories into a temporary staging area. For example: cd /target_dest_dir/db cp -RH /source_dir/db/* Alternatively. Copy the database (. and that the database node files are owned by the target ORACLE user. as following symbolic links is not the default behavior on all platforms. Ensure the application tier files copied to the target system are owned by the target APPLMGR user. On most UNIX platforms.

If any other profile options are set to instance specific values. Using the Workflow Administrator Web Applications 3. Review the tables and columns listed in Table 4 to check for any instance-specific data in the Workflow configuration on the target system. paths.pl appsTier Section 3: Finishing Tasks This section lists tasks that may be necessary. update the target system with the new printer settings now. 2. You will be prompted for specific target system values such as SID. and ports. depending on your implementation and the intended use of the cloned system. 1.pl dbTier Configure the target system application tier server nodes Log on to the target system as the APPLMGR user and enter the following commands: $ cd [COMMON_TOP]/clone/bin $ perl adcfgclone. you must update them manually. Table 4: Workflow configuration settings Table Name Column Name Column Value Details Value starts with http://[old web host]: Update to new web host. Update printer settings If the new cloned system needs to utilize different printers. Cloning an Oracle Applications instance will not update the host and instancespecific information used by Oracle Workflow. Update Workflow configuration settings WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE WF_ITEM_ATTRIBUTE_VALUES WF_SYSTEMS TEXT_VALUE GUID . Configure the target system database server Log on to the target system as the ORACLE user and enter the following commands: $ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin $ perl adcfgclone. Update profile options Rapid Clone updates only site level profile options.Configure the target system Run the following commands to configure the target system. Value starts with "http://[old web host]: Update to new web host.

To modify it. Option 1: Refreshing a Target System . Update database link with the new database global name. FND_CONCURRENT_REQUESTS LOGFILE_NAME FND_CONCURRENT_REQUESTS OUTFILE_NAME 4. Update with the new web host name. reconfigure the Target by following the SSL/SSO documentation. Re-Implement SSL and SSO configuration If the Source System was SSL or SSO enabled.responsibility. 5. If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN was not null in the source system. create a new system defined as the new global database name. update that value to reflect the new domain name. Verify the APPLCSF variable setting Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to a suitable directory. WF_AGENTS ADDRESS FND_FORM_FUNCTIONS FND_FORM_FUNCTIONS WEB_HOST_NAME Update to point at WEB_AGENT_NAME the new PL/SQL listener name. change the value of the s_applcsf variable in the context file and then run AutoConfig. WF_SYSTEMS NAME Replace value with the database global name. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS 6. Update with the correct path to the logfile directory. Section 4: Advanced Cloning Options This section describes various advanced cloning procedures that may need to be employed in the appropriate circumstances. Update with the new directory path on the target system.

pl appsTier [APPL_TOP target context file] Where APPL_TOP target context file is [INST_TOP]/appl/admin/[Target CONTEXT_NAME]. This means that all files . Configure the target system application tier server nodes by logging on to the target system as the APPLMGR user and entering the following commands: $ cd [COMMON_TOP]/clone/bin $ perl adcfgclone. If refreshing the database.You may need to refresh the target system periodically to synchronize it with changes to the source system. Specify the existing target system context file when running adcfgclone. Copy the source system to the target system. If the RDBMS ORACLE_HOME or the database needs to be refreshed. a.pl dbTier [Database target context file] Where Database target context file is [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME]. If the application tier file system if the APPL_TOP. 2. COMMON_TOP. 3. perform the following steps as described in previous sections: 1.xml 4. Configure the target system database server by logging on to the target system as the ORACLE user and entering the following commands to configure and start the database: $cd [RDBMS ORACLE_HOME]/appsutil/clone/bin perl adcfgclone. copy the database node file system.xml b. the ORACLE_HOME should be refreshed at the same time. all APPL_TOPs are unified APPL_TOPs. copy the portion of the application tier file system that has been updated b. or technology stack needs to be refreshed. As of Release 12.pl commands. Perform the standard finishing tasks. Prepare the source system. To refresh the target system. Option 2: Cloning a Multi-Node System This procedure allows the source system or target system to be a multi-node system. Configure the target system. Note: Back up the target context file on the target system before refreshing the database or application tiers. a.

Carry out these steps on all source and target nodes. To add non-shared application tier nodes. or different services. Option 4: Cloning an Oracle RAC system . After adcfgclone. copy and configure the cloned Applications system.pl completes.pl Note: After adding new nodes. When creating more than one application tier node on the target system.required for all application tier services are installed on every application tier node. source the Applications environment and run the following commands on the target system: $ cd [COMMON_TOP]/clone/bin $ perl adaddnode. Perform the standard prerequisite tasks. Multiple application tier nodes are distinguished from each other by the services running. Perform a full clone (Prepare. follow the instructions in My Oracle Support Knowledge Document 384248. Prepare the source system.1 for details of how to set up load balancing. See the Oracle Applications Manager on line help for instructions on how to accomplish this. 2. Perform the required finishing tasks Option 3: Adding a New Node to an Existing System You can use Rapid Clone to clone a node and add it to the existing Applications system. 4. Section 4: Adding a node to a Shared Application Tier File System. 3. only one copy of the applications tier node files needs to be copied to the target system. Thus. refer to My Oracle Support Knowledge Document 380489. Follow the instructions in the Application tier part of Cloning Tasks. follow these steps: 1. execute the copy and configure steps as on the primary node. 2. 2. copy and configure steps) of the database node and primary application tier node. To add shared application tier nodes on the target system. Specify the services to start on each target Applications tier node when responding to the prompts during the configuration step. 1. Prepare. you first need to authorize the new node to access the database through SQL*Net. Carry out the previously-described cloning tasks. The new node can run the same services as the source node.1. copy it to the new node and configure it. 3. 1. Note: If SQL*Net Access security is enabled in the existing system. regardless of whether a shared file system is being used on the source or target system. a process also known as scale up or scale out.

Snap View. This section documents the steps needed to allow manual creation of the target database control files within the Rapid Clone process. . Configure the [RDBMS ORACLE_HOME] $ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin $ perl adcfgclone. Log on to the target system as the ORACLE user 2. Typical scenarios are when system downtime is not feasible.For instructions on how to Clone RAC-Enabled Systems with Rapid Clone. Option 6: Cloning the Database Separately Some situations require the database to be recreated separately.1 for instructions on how to perform this task. or 'dll' for Windows. Option 5: Adding a Node to an Existing Oracle RAC Cluster From Release 12. Start the target database in open mode 5. 6. or Mirror View.1.pl dbTechStack 3. such as RMAN restore. Follow the complete steps in Cloning Tasks.sql [libext] Where [libext] should be set to 'sl' for HP-UX. you copy and recreate the database using your preferred method. Create the target database control files manually In this step. Run the library update script against the database $ cd [RDBMS ORACLE_HOME]/appsutil/install/[CONTEXT NAME] $ sqlplus "/ as sysdba" @adupdlib. Refer to My Oracle Support Knowledge Document 388577.pl dbconfig [Database target context file] Where Database target context file is: [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME]. or advanced database replication tools like RMAN are being used to copy the database in hot backup mode. Rapid Clone is no longer used to migrate a database tier to Oracle RAC.xml. but replace Step 3a (Configure the target system database server) with the following steps: 1. 'so' for any other UNIX platform. Configure the target database The database must be running and open before performing this step. refer to My Oracle Support Knowledge Document 559518. This method needs to be used for databases located on raw partitions. without using Rapid Clone. or when cloning a hot backup. Flash Copy. 4. $ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin $ perl adcfgclone.

2010 Description • • • • • • Feb 15. Added Reference to Patch 8246709 for OracleAS 10.1.1 on Section 1.Note: The dbconfig option will configure the database with the required settings for the new target. Moved Appendix A into the Advanced Cloning Options and added some more details. Change Log Date Jan 03.1 Replaced RC Consolidated patch with 9171651 Added Patch 9462233 for 12. Step 3. 2009 Mar 13. 2010 Apr 24. 2009 Apr 09. Step 5. .4 Oracle Home. 2009 Feb 13. Added Clarification for MS Windows (32-bit) on Patch 8221919. 2011 Dec 29. 2009 Jan 22.0 and 12. 2010 Sep 24. 2009 Mar 02. Added Patch 7699109 on Section 1. Corrected hyperlink in Section 4. Step 5 Addressed general formating issues Added clarifications for versions of ZIP and UNZIP in Section 1 Added additional step for SSL/SSO in Section 3 Replaced Rapid Clone Consolidated Patch with 8360494 (JAN/2010) Removed other patches since they are now included in 8360494 Restructured document. 2009 May 08.1 on Section 1. Replaced Rapid Clone Consolidated Patch with 7164226 (May 2009).3. Added Patch 8221919 on Section 1. • • • • • • • • • Corrected URLs for updates. 2010 • • • • Jun 24. but it will not recreate the control files.0 and 12. Step 5 Clarified AD Patches for 12.com Added Patch 9833058 for 12.1.oracle. 2009 Feb 16.0 and 12. Added Reference to Note 783188. 2009 Jun 23. Step 5.

2007 Jul 30.1 for RAC cloning instructions. Replaced Rapid Clone Consolidated Patch with 6776948 (Jul 2008). Included clarification on how to use cp command to preserve symbolic links. Removed reference to HP OpenVMS Alpha since this is not a Jul 29.52 to Section 1. Step 2. Modified cp command usage.4 and latest Rapid Clone consolidated patch. Included Windows Itanium patch. Minor layout changes. Added requirement to apply the latest AD Patch.A.2009 Aug 07. Removed Windows desupport notice. Removed Patch 6854328 since its included on 6776948 (Jul 2008). 2008 Dec 18. Added tracking bug number 7275583 to add a node while cloning a RAC system. 2007 Jun 25. 2008 Feb 28. Added tracking bug number 7276544 to add a node on an existing RAC system without cloning. 2007 May 18. Added Unzip 5.DELTA. Added AD. 2008 • • • • Added Clarification for RUP2 or higher. Removed Rapid Clone restriction for RAC-enabled Systems in Section 4. Added Warning to re-run post-clone steps after patching the system. Steps 4 and 5. Step 2. Added clarification to backup the context file when refreshing a target system on 4. Adjusted heading format in Section 2. Fixed post patch steps on note box. Added reference to Document 559518. Step 5. Included step to verify OS requirements. 2007 • • • Dec 17.1. 2008 Jan 25. 2007 Dec 07. 2008 • • • • • • • • • Mar 24. 2007 • • • • • • . Included Patch 6854328 for Windows 64-bit in Section 5.

Related Products • Errors ORA-201 Back to top Rate this document Top of Form 406982.1 by Oracle E-Business Suite Development Copyright 2007. Created initial document. 2007 Feb 22. Step 7. 2007 • Corrected link to Oracle Applications Maintenance Utilities on Section 1. All rights reserved. Added note that using Rapid Clone on Windows is not currently supported. Added reference to Note 380489. 2007 Feb 23.certified or supported platform for any tier with Release 12. May 10. • • • My Oracle Support Knowledge Document 406982. 2009.1 for Load Balancing.1 Thank you for yo Provide feedback Oracle E-Business Suite > Applications Technology > Lifecycle Management > Oracle Applications Manager . 2010 Oracle and/or its affiliates. 2007 Jan 24.

How easy was it to find this document? Very easy Somewhat easy Not easy Cancel Bottom of Form .Article Rating Rate this document Excellent Good Poor Did this document help you? Yes No Just browsing Comments Prov ide f eedbac k f or this artic le. Pleas e us e 'Contac t Us ' f or other f eedba Important Note: this feedback is anonymously visible to other customers until processed by Oracle Support.

Sign up to vote on this title
UsefulNot useful