1) 1
May 2011
Cloning creates an identical copy of an existing Oracle Applications System. There are various reasons for
cloning an Oracle Applications System such as:
This document describes the process of cloning an Oracle Applications Release 11i System. The most
current version of this note is document 230672.1 on My Oracle Support. A FAQ is also available
indocument 216664.1 on My Oracle Support.
Section 1: Prerequisites
Tasks to perform before using Rapid Clone.
Section 2: Clone Oracle Applications 11i
Tasks to prepare, copy, configure, and verify a cloned Applications System.
Section 3: Finishing Tasks
Tasks to complete the cloning process.
Section 4: Advanced Cloning Methods
Tasks for advanced options such as refreshing and Multi-Node cloning.
Conventions
Convention Meaning
Source System Applications System being cloned.
Target System Applications System being created as a copy of the Source.
User which owns the Applications File System (APPL_TOP and Application
APPLMGR
Tier technology stack)
User which owns the Database File System (RDBMS ORACLE_HOME and
ORACLE
Database files).
The CONTEXT_NAME variable refers to the name of the Applications Context
file. For Systems installed with Rapid Install 11.5.8 or earlier, this value will
CONTEXT_NAME
typically be set to [SID]. For new AutoConfig or Rapid Clone customers,
CONTEXT_NAME will be set to [SID]_[HOSTNAME].
Monospace Text Represents command line text. Type this command exactly as shown.
Cloning Oracle Application Rel 11i, with Rapid Clone (ID 230672.1) 2
Section 1: Prerequisites
Before cloning, prepare the Source System by applying patches and running AutoConfig.
Min.
Software Location Details
Version
Apply OUI22 patch 5035661 on every iAS and RDBMS
Oracle
All Source ORACLE_HOME to be cloned. Do not apply the patch to
Universal 2.2.0.19
System Nodes your RDBMS ORACLE_HOME, if you have Oracle 10g or
Installer
higher installed.
Use the Perl shipped with iAS1022 and RDBMS 9i if
Source and
available or download it from Perl.com. Perl must be in the
Perl 5.005 Target Database
PATH before cloning. Windows users: do not use Perl from
Nodes
MKSToolKit.
If the RDBMS ORACLE_HOME was not installed using
Source Database
JRE 1.1.8 Rapid Install, install JRE 1.1.8 into the [RDBMS
Node
ORACLE_HOME]/jre/1.1.8 directory.
Windows users only: install JRE 1.3.1 into the [RDBMS
Source Database
JRE 1.3.1 ORACLE_HOME]/jre/1.3.1 directory. SeeAppendix A for
Node
installation instructions.
Target middle-
Refer to Upgrading to JDK 1.3 with Oracle Applications 11i
JDK 1.3.1 Tier Applications
on My Oracle Support for instructions.
Nodes
2.3 Download from InfoZip. Zip must be in your PATH. If using
Zip (or All Source Nodes files bigger than 2Gb, you should use InfoZip ZIP 3.0 or
higher) higher.
5.52 Download from InfoZip. UnZip must be in your PATH. If
UnZip (or All Source Nodes using files bigger than 2Gb, you should use InfoZip UNZIP
higher) 5.52 or higher.
OS utilities (see 11i Install Manual) must be in the the PATH
OS utilities N/A All Target Nodes when running adcfgclone.pl (Unix: make,ld,cc,ar - Windows:
gnumake,link,cc,cmd)
2. Apply the latest AD Minipack
Apply patch 6502082 (11i.AD.I.6) or higher.
Please refer to My Oracle Support to obtain the latest MiniPack available for AD.
3453499 : 11i.ADX.F
9171650 : 11i RAPIDCLONE CONSOLIDATED FIXES JUL/2010
9874305 : ADMKAPPSUTIL.PL COMPLAINS ABOUT UNZIP VERSION
10182813 : Required if using 11gR2 version of the Database
8977646 : Required for Windows Platforms
Attention: Every time that a new Rapid Clone or Autoconfig patch is applied on the APPL_TOP, the
RDBMS ORACLE_HOME must be updated with the files included on those patches.
Follow the instructions in section Maintaining System Configuration in document 165195.1 on My Oracle
Support to synchronize the Rapid Clone and Autoconfig files on the RDBMS ORACLE_HOME.
Execute the following commands to prepare the Source System for cloning.
cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
perl adpreclone.pl dbTier
cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
perl adpreclone.pl appsTier
[APPL_TOP]
[OA_HTML]
[OA_JAVA]
[OA_JRE_TOP]
[COMMON_TOP]/util
[COMMON_TOP]/clone
[COMMON_TOP]/_pages (when this directory exists)
[806 ORACLE_HOME]
[iAS ORACLE_HOME]
Note: Unix/Linux users, make sure that the softlinks are preserved when copying. Additionally, verify the
permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root (i.e.
nmo, nmhs, nmb, etc).
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier
cd [COMMON_TOP]/clone/bin
perl adcfgclone.pl appsTier
Column
Table Name Column Value Details
Name
WF_NOTIFICATION_AT TEXT_VALUE Value starts with http://[old web host] : Update to new
Cloning Oracle Application Rel 11i, with Rapid Clone (ID 230672.1) 6
Attention: Backup the Target Context File on the Target System before refreshing the dbTier or appsTier.
To refresh the Target System, perform the following steps as described in previous sections:
Copy the Application Tier File System if the APPL_TOP, 806 ORACLE_HOME, or
iAS ORACLE_HOME needs to be refreshed. Copy the portion of the Application
Tier File System which has been updated.
Copy the Database Tier File System if the RDBMS ORACLE_HOME or the
Database needs to be refreshed. If refreshing the Database, the ORACLE_HOME
should be refreshed at the same time.
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier [Database Target Context
File]
cd [COMMON_TOP]/clone/bin
perl adcfgclone.pl appsTier [Appltop Target Context
File]
d. Finishing Tasks
2. Cloning a Single-Node System to a Multi-Node System
This procedure allows the original Single-Node System to be cloned into a Multi-Node System. An
Applications System comprises five Server types:
During the Single-Node to Multi-Node cloning process, each of these Servers can be placed on its
own Node, resulting in a Multi-Node Target System.
f. Perform prerequisites
Cloning Oracle Application Rel 11i, with Rapid Clone (ID 230672.1) 8
h. Finishing Tasks
Note: Another way of changing a Single-Node System to a Multi-Node System is to share the
APPL_TOP. See document 233428.1 on My Oracle Support for details.
To clone a Multi-Node System to a Multi-Node System, perform the cloning process on each Node.
For example, if the Source System contains three Nodes, perform the cloning process three times.
a. Prepare the Source System, copy it to the new Node and configure it.
b. After adcfgclone.pl completes, Source the Applications environment and run the following
commands on the Target System:
cd [COMMON_TOP]/clone/bin
perl adaddnode.pl
Note: If the SQL*Net Access security is enabled in the existing System (enabled by default
from 11i10), you first need to authorize the new Node to access the Database through SQL*Net.
See Managed SQL*Net Access from Hosts in document 281758.1 on My Oracle Support for
instructions on how to achieve this from OAM.
You can use Rapid Clone to clone a Multi-Node System to a Single-Node System (or a Multi-Node
System with fewer Nodes) by merging the APPL_TOPs fileSystem together. Follow the procedure
for Merging existing APPL_TOPs in document 233428.1 on My Oracle Support.
Attention: The following steps apply only for 9i RAC Clusters. For 10g or 11g RAC
environments, please follow the instructions in Document 760637.1.
Note: For complete details on the certified RAC scenarios for E-Business Suite Cloning, refer
to Document 783188.1 available in My Oracle Support.
To clone a RAC System, perform the following tasks:
Note: You also have the option to clone each ORACLE_HOME from the Source RAC cluster
to the Target cluster. In that case, run adpreclone.pl on every ORACLE_HOME.
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier
This step configures the first Node of the Target System RAC cluster and recreates
the Database control files. The prompts, however, will gather information about
every Node in the Target RAC cluster and the data will be re-used when configuring
each subsequent Node in the next step.
For each remaning RDBMS ORACLE_HOME in the Target System, run the
Cloning Oracle Application Rel 11i, with Rapid Clone (ID 230672.1) 10
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier
Note: To clone from RAC to non-RAC, follow the same above steps but copy the master
ORACLE_HOME to one Target Node only, and answer "No" to the question "Target instance is
a Real Application Cluster (RAC) instance (y/n)", when prompted by adcfgclone.pl.
Attention: The following steps apply only for 9i RAC Clusters. For 10g or 11g RAC
environments, please follow the instructions in Document 760637.1.
Note: For complete details on the certified RAC scenarios for E-Business Suite Cloning, refer
to Document 783188.1 available in My Oracle Support.
Perform the following tasks:
a. Choose any one of the ORACLE_HOMEs in the existing cluster and run the following
command:
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier
c. On the init.ora, set the variable "cluster_Database_instances" to match the new number of
Nodes.
Note: After the RAC conversion, the context variable %s_dbClusterInst% will need to be set on
the Database Context files to reflect the new number of Nodes.
From the OAM Context Editor, set the variable with the new number and run Autoconfig on
each ORACLE_HOME.
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier
Cloning Oracle Application Rel 11i, with Rapid Clone (ID 230672.1) 11
Note: You will be prompted for information about all the Nodes forming the new cluster and
asked to perform the next step before completing adcfgclone.pl on this Node.
When instructed so by the previous step, log on to every Node from the original
cluster and run the following command on each of them:
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl addracNode [Context File]
If you are adding more than one Node to the original cluster, log on to each of the
remaining new Nodes and run
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier
a. Perform prerequisites
Perform these steps on Node A and and every Target Nodes.
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTechStack
Where [libext] should be set to 'sl' for HP-UX, 'so' for any other UNIX platform,
or 'dll' for Windows.
cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbconfig [Target Context File]