Section 1: Prerequisites (If you are using 11.5.10 then Prerequisites not required)

Before cloning, prepare the source system by applying patches and running AutoConfig.

Step: 1 Verify source and target nodes software versions ( Read Metalink Note:230672.1 for More Details)

Step: 2 Apply the latest AutoConfig Template patch

Update the Oracle Applications file system ( Source System) with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes. ( Read Metalink Note:165195.1 for details)

Step:3 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 application tier server nodes :

• 3453499 (11i.ADX.F)
• 5225940 (Post ADX.F Fixes)

Step:4 Setup Rapid Clone on the Applications Tier

• If the source Applications system was created with Rapid Install version 11.5.5 or earlier and has not been migrated to AutoConfig, follow the instructions   Migrating to AutoConfig on the Applications Tier in document 165195.1 on OracleMetaLink.
• All users must run AutoConfig on the Applications Tier, follow the instruction Maintaining System Configuration in document 165195.1 on OracleMetaLink.

Step:5 Setup Rapid Clone on the Database Tier

Implement AutoConfig in the RDBMS ORACLE_HOME (Follow the instructions in section Migrating to AutoConfig on the Database Tier in document 165195.1 on OracleMetaLink. Follow steps 1 and 4 of Section 7 in the AutoConfig document for all versions of RapidInstall and every time you apply a new version of the Rapid Clone patch.

Step:6 Maintain Snapshot information

Log in to each Application Tier Node as the APPLMGR user and run Maintain Snapshot information in AD Administration.

Section 2: Clone Oracle Applications 11i

There are three steps to the cloning process:

Step:1 Prepare the Source System

1. Prepare the source system database tier for cloning
   Log on to the source system as the ORACLE user and run the following commands:
   cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
perl adpreclone.pl dbTier
2. Prepare the source system application tier for cloning
   Log on to the source system as the APPLMGR user and run the following commands on each node that contains an APPL_TOP:
   cd <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>
perl adpreclone.pl appsTier

Step:2 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.  Ensure the application tier files copied to the target system are owned by the target APPLMGR user, and that the database tier files are owned by the ORACLE user.

Step:3 Configure the Target System

Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, Paths, Ports, etc)

1. Configure the target system database server
   Log on to the target system as the ORACLE user and type the following commands to configure and start the database:
   cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
perl adcfgclone.pl dbTier
2. Configure the target system application tier server nodes
   Log on to the target system as the APPLMGR user and type the following commands:
   cd <COMMON_TOP>/clone/bin
perl adcfgclone.pl appsTier

Section 3: Finishing Task (Read Metalink Note:230672.1 for More Details)

This section lists tasks that may be necessary depending on your implementation and the intended use of the cloned system.

Update profile options
Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually.

Update printer settings
If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.

Update workflow configuration settings
Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.

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 an acceptable directory. To modify it, change the value of s_applcsf in the contextfile and run AutoConfig.

Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
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, update that value to reflect the new domain name.

Windows users only reboot the target machine
Once cloning is completed reboot to enable the services.