You are on page 1of 14

Cloning Oracle Applications Release 11i with

Rapid Clone
Doc ID: 230672.1 Type: WHITE PAPER
Modified Date : 22-JAN-2009 Status: PUBLISHED
View Change log

Cloning Oracle Applications Release 11i

with Rapid Clone
January 2009

Cloning creates an identical copy of an existing Oracle Applications system.

There are various reasons for cloning an Oracle Applications system such as:

• Creating a copy of the production system for testing updates.

• Migrating an existing system to new hardware.
• Creating a stage area to reduce patching downtime.

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
OracleMetaLink. A FAQ is also available in document 216664.1 on

Note: Rapid Clone is currently not supported on Windows Itanium and

HP OpenVMS Alpha.
Attention: Windows users. This document typically uses UNIX syntax
when specifying directories; Please substitute the appropriate Windows

• 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.


Convention Meaning
Source system Applications system being cloned.
Applications system being created as a copy
Target system
of the source.
APPLMGR User which owns the applications file
system (APPL_TOP and application tier
technology stack)
User which owns the database file system
The CONTEXT_NAME variable refers to
the name of the Applications Context file.
For systems installed with Rapid Install
CONTEXT_NAME 11.5.8 or earlier, this value will 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.
Text enclosed in angle brackets represents a
<> variable. Substitute a value for the variable
text. Do not type the angle brackets.

Section 1: Prerequisites

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

1. Verify source and target nodes software versions

In addition to the Oracle Applications software requirements (see Installing
Oracle Applications Release 11i Part No. B10638-01), the following
software component versions must exist on the source and/or target nodes.
The location column indicates the node where the software component
must be present.
Software Location Details

Apply OUI22 patch 5035661 on

every iAS and RDBMS
Oracle All source ORACLE_HOME to be cloned.
Universal system Do not apply the patch to your
Installer nodes RDBMS ORACLE_HOME, if you
have Oracle 10g or higher
Use the Perl shipped with iAS1022
Source and and RDBMS 9i if available or
target download it from Perl
Perl 5.005
database must be in the PATH before
nodes cloning. Windows users: do not
use Perl from MKSToolKit.
was not installed using Rapid
Install, install JRE 1.1.8 into the
JRE 1.1.8 database
Windows users only: install JRE
Source 1.3.1 into the <RDBMS
JRE 1.3.1 database ORACLE_HOME>/jre/1.3.1
node directory. See Appendix A for
installation instructions.
Refer to Upgrading to JDK 1.3
JDK 1.3.1 with Oracle Applications 11i on
OracleMetaLink for instructions.
All source Download from InfoZip. Zip must
Zip 2.3
nodes be in your PATH for cloning.
OS utilities (see 11i Install
Manual) must be in the the PATH
OS All target
N/A when running (Unix:
utilities nodes
make,ld,cc,ar - Windows:
2. Apply the latest AD Minipack
Apply patch 6502082 (11i.AD.I.6) or higher.
Please refer to OracleMetaLink to obtain the latest MiniPack available for
3. Windows users only:
Apply patch 2237858 to enable long file names support.
4. 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.
Please refer to document 165195.1 on OracleMetaLink to obtain the latest
Autoconfig Template Rollup Patch available.
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 application tier server nodes :
o 3453499 : 11i.ADX.F
o 7307102 : Required for Windows 32 Bit
o 7425146 : Required for Windows x86-64 (EM64T)
6. Setup Rapid Clone on the Applications Tier

a. 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).
b. All users must run AutoConfig on the Applications Tier (see section 5:
Maintaining System Configuration in document 165195.1 on
2. 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).
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 OracleMetaLink to synchronize the Rapid Clone and
Autoconfig files on the RDBMS ORACLE_HOME.
3. Maintain Snapshot information
Log in to each Application Tier Node as the APPLMGR user and run
Maintain Snapshot information in AD Administration.
See Oracle Applications Maintenance Utilities for more information.

Section 2: Clone Oracle Applications 11i

Use Rapid Clone to create template files for cloning on the source system.
After the source system is copied to the target, Rapid Clone updates these
templates to contain the new target system configuration settings. Rapid Clone
will not change the source system configuration.

There are three phases to the cloning process:

1. Prepare the Source System

Execute the following commands to prepare the source system for cloning.
a. Prepare the source system database tier for cloning
Log on to the source system as the ORACLE user and run the following
perl dbTier
b. 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 appsTier
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.
a. Copy the application tier file system
Log on to the source system application tier nodes as the APPLMGR
 Shut down the application tier server processes
 Copy the following application tier directories from the
source node to the target application tier node:
 <COMMON_TOP>/util
 <COMMON_TOP>/clone
 <COMMON_TOP>/_pages (when this directory
b. Copy the database tier file system
Log on to the source system database node as the ORACLE user.
 Perform a normal shutdown of the source system
 Copy the database (DBF) files from the source to the
target system
 Copy the source database ORACLE_HOME to the target
 Start up the source Applications system database and
application tier processes
Note: Unix/Linux users, make sure that the softlinks are preserved when
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)
a. 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 dbTier
b. 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 appsTier

Attention: Windows user only: add <806 ORACLE_HOME>\bin to

the system path before running this step.

Section 3: Finishing Tasks

This section lists tasks that may be necessary depending on your

implementation and the intended use of the cloned system.

1. 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.
2. Update printer settings
If the new cloned system needs to utilize different printers, update the
target system with the new printer settings now.
3. 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.
Column Value
Table Name Column Name
Value starts with
Update to new web host
Value starts with
WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE "http://<old web host> :
Update to new web host
Create a new system
defined as the new global
database name using the
Workflow Administrator
Web Applications
Value needs to be
WF_SYSTEMS NAME replaced with the
database global name
Update database link with
WF_AGENTS ADDRESS the new database global
Update with the new web
host name
Update to point at the
Update with the correct
Update with the new
target system
4. 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.
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.
6. Windows users only reboot the target machine
Once cloning is completed reboot to enable the services.

Section 4: Advanced Cloning Options

This section describes advanced cloning procedures.

1. Refreshing a target system

You may need to refresh the target system periodically to synchronize it
with changes from the source.
Attention: Backup the target context file on the target system before
refreshing the dbTier or appsTier.
2. To refresh the target system, perform the following steps as described in
previous sections:
a. Prepare the Source System
b. Copy the Source System to the Target System
o 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.
o 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
c. Configure the Target System
Specify the existing target system context file when running commands:
o perl dbTier <Database target
context file>
where database context file is:
<RDBMS ORACLE_HOME>/appsutil/<Target
o perl appsTier <Appltop target
context file>
where appltop context file is:
<APPL_TOP>/admin/<Target CONTEXT_NAME>.xml
d. Finishing Tasks
3. 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:

o Database server (database tier)

o Forms server (application tier)
o Web server (application tier)
o Concurrent Processing server (application tier)
o Administration server (application tier)

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.

a. Perform prerequisites
Perform these steps on all source and target nodes.
b. Clone Oracle Applications 11i
Prepare, copy and configure the cloned Applications System. When
creating more than one application tier server node from a single node
system, the copy and configure steps must be performed on each target
node. You can specify the server type for each target node while
answering the prompts during the configuration step.
The database ORACLE_HOME and database only need to be copied to
the node on which the database will be run.
c. 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
OracleMetaLink for details.
4. Cloning a multi-node system to a multi-node system with same
number of nodes
A multi-node system can be cloned provided the number of nodes and
distribution of servers in the target system matches that of the source

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.

o Clone source system node 1 to target system node 1.

o Clone source system node 2 to target system node 2.
o Clone source system node 3 to target system node 3.
Attention: The database server node must be cloned first.
2. Adding a new node to an existing system
You can use Rapid Clone to clone a node and add it to the existing
Application System. The new node will run the same or a subset of the
server types running on the source node. Follow the instructions in the
Application Tier part of Clone Oracle Applications 11i:
o Prepare the source system, copy it to the new node and
configure it.
o After completes, source the Applications
environment and run the following commands on the target system:
o cd <COMMON_TOP>/clone/bin
o perl
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 OracleMetalink for
instructions on how to achieve this from OAM.
3. Reducing the number of nodes of a multi-node system (merge
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 OracleMetaLink.
4. Cloning a RAC system
You can use Rapid Clone to clone a RAC system. While cloning, you have
the possibility to remove or add nodes to the cluster in the target RAC
system. To clone a RAC system, perform the following tasks:

a. Verify the prerequisites

o Apply TXK patch 3571388 (AutoConfig support for
Oracle RAC instances)
o Migrate the source system cluster ORACLE_HOMES to
AutoConfig as documented in document 165195.1 on
b. Prepare the Source System
Choose one of the ORACLE_HOMEs on the source cluster. This
ORACLE_HOME will be used as a master to create all the target
cluster system ORACLE_HOME. Run "perl dbTier" on
Note: You also have the option to clone each ORACLE_HOME from
the source RAC cluster to the target cluster. In that case, run on every ORACLE_HOME.
c. Copy the Source System to the Target System
o Copy the master ORACLE_HOME from the source
system to each node that will compose the target cluster. For
example, if your source RAC system had 2 nodes, and you want to
clone it to a 3 node target RAC system, you should copy the source
master ORACLE_HOME to the 3 nodes on the target system.
o Copy the database files from the source to target system.
d. Configure the Target System
o Log on to any ORACLE_HOME in the target cluster and
 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.

o For each remaning RDBMS ORACLE_HOME in the

target system, run the following command as the ORACLE file
system owner:
 dbTier
o If your database is version 10g or higher, run the
following commands to register the database and the instance to the
cluster manager .
 srvctl add database -d <database_name>
-o <oracle_home>
 srvctl add instance -d <database_name> \
-i <instance_name> -n <host_name>
Note: If the cluster manager is not on Linux (ORACM) or the database
is version 10g or higher, manually start up the cluster manager on the
target system before running
e. Clone the application tier
Follow the steps in section 2 to prepare, copy and configure the
application tier. When prompted for the database SID, specify any one
of the RAC service names.

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
5. Adding a node to an existing RAC Cluster
You can use Rapid Clone to add one or several nodes to an existing RAC
Cluster. Perform the following tasks:

f. Choose any one of the ORACLE_HOMEs in the existing cluster

and run "perl dbTier" on it. This ORACLE_HOME will
be used as a master to create the additional node(s).

g. Copy the master ORACLE_HOME filesystem to the new


h. 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.
j. Reconfigure the RAC Cluster to include the new node(s):
o Log on to the new node, or any one of the new nodes if
adding more than one, and run the following command:
 cd /appsutil/clone/bin
 perl dbTier
Note: You will be prompted for information about all the nodes
forming the new cluster and asked to perform the next step before
completing on this node.
o 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 /appsutil/clone/bin
 perl addracnode <context
o Go back to the first node and complete
o If you are adding more than one node to the original
cluster, log on to each of the remaining new nodes and run
 cd /appsutil/clone/bin
 perl dbTier

Note: If the cluster manager is not on Linux (ORACM) or the database

is version 10g or higher, manually start up the cluster manager on the
target systems before running
6. Cloning a Shared File System
You can use Rapid Clone to clone a shared APPL_TOP system. Since all
the nodes share a unique APPL_TOP you only need to fully clone one of
the source system nodes to its target machine and add more nodes directly
sharing the APPL_TOP on the target system. Choose one of the shared
APPL_TOP nodes on source system (the rest of this section will refer to it
as Node A) and perform the following tasks:

k. Perform prerequisites
Perform these steps on Node A and and every target nodes.
l. Clone Oracle Applications 11i
Perform a full clone (Prepare, copy and configure steps) of the
Database Tier and Node A (Application tier).
m. Add the shared file system nodes to the target system
On the target system, follow the instructions for adding a node to a
shared APPL_TOP system in document 233428.1 on OracleMetalink
and add more nodes sharing the target system APPL_TOP to match the
source system topology.
Appendix A: Install JRE 1.3.1 into RDBMS ORACLE_HOME

Windows customers will need to perform the following steps:

• Download JRE 1.3.1 from Sun Microsystems.

• Run the install executable
• When prompted for the location to install jre, click browse and enter the
• Accept the default installation options.

JRE 1.3.1 will be installed into the <RDBMS ORACLE_HOME>\jre\1.3.1


Appendix B: Recreating database control files manually in Rapid


This Appendix documents the steps to allow manual creation of the target
database control files within the Rapid Clone process. Examples of when to use
this method are for databases on raw partitions or hot backup cloning. Replace
section 2.3a (Configure the target system database server) with the following

• Log on to the target system as the ORACLE user

• Configure the <RDBMS ORACLE_HOME>
o cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
o perl dbTechStack
• Create the target database control files manually
• Start the target system database in open mode
• Run the library update script against the database
o cd <RDBMS ORACLE_HOME>/appsutil/install/<CONTEXT
o sqlplus "/ as sysdba" @adupdlib.sql <libext>
where <libext> is "sl" for HP-UX, "so" for any other UNIX platform and
not required for Windows.
• Configure the target database (the database must be open)
o cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
o perl dbconfig <target context file>
where target context file is:

<RDBMS ORACLE_HOME>/appsutil/<Target CONTEXT_NAME>.xml

Change Log
Date Description
 Removed Unsupported statement for Windows x86-64 (EM64T)
January 22, 2008 and updated the platform name according to the Platform Naming
October 16, 2008  Added Required Patches for Windows 32 Bit and AM64
 Replaced Rapid Clone Consolidated Patch with 6718351
August 07, 2008  Removed Patch 6913832 since its included on 6718351 (JUL/2008)
 Removed Patch 6438830 since its included on TXK.S (6372396)
now released in Metalink .
 Added Patch 6913832 required for HP-UX PA-RISC 64-bit and
March 26, 2008
SOLARIS 64-bit
February 4, 2008  Added Patch 6438830 required for Solaris Intel
January 25, 2008  Added AD.I.6 and latest Rapidclone Consolidated Patch
 Added clarification to backup the context file when refreshing a
December 17, 2007
target system on 4.1
May 16, 2007  Added clarification to set "cluster_database_instances" on 4.7
May 4, 2007  Added Patch 5972212 required for SLES 10.
 Added a Note to update RDBMS ORACLE_HOME after patching
March 26, 2007
Rapid Clone or Autoconfig.
March 25, 2007  Added a step to apply the latest Minipack for AD.
 Removed HP Tru64 desupport note since the issues have been fixed
January 08, 2007
on TXK-O.
 Added HP OpenVMS Alpha and HP Tru64 as non Supported
December 04, 2006
 Added Windows x86-64 (AMD64/EM64T) as non Supported
August 16, 2006  Modified Section 1, Step 6 to point to correct Section on Document
 Added Run Snapshot Information in prereq section.
June 15, 2006  Added Post ADX.F Fixes Patch in prereq section.
 Added TXK Autoconfig Template RollUp Patch in the prereq
May 9, 2006
April 25, 2006  Replaced OUI22 patch 4017155 with 5035661 in the prereq section.
 New ADX patch 3453499.
October 14, 2005  Added section with instructions for adding a RAC node to an
existing RAC cluster.
June 13, 2005  Added 10g RAC cloning steps to section 4.6.
 New ADX patch 4175764.
 Added section 1.7 with instructions for cloning a shared
March 09, 2005
APPL_TOP system.
 Changed AppendixB to run with 'dbconfig' option
 Updated Rapid Clone patch to 4068109
December 14, 2004
 Updated Step 1.5 to point to Section 5 in the AutoConfig note
 Updated Rapid Clone and OUI22 patch numbers
December 02, 2004  Added instructions for RAC cloning (Section 4.6)
 Added Note about SQL*Net Access Security (Section 4.4).
 Changed OUI22 patch to 3890564 in the prereq section.
October 19, 2004  Updated Section 2.2.a to copy COMMON_TOP/_pages when it
August 16, 2004  Changed Rapid Clone patch number to 3817226 (ADX.E.1)
 Re-worded Sections 4.3 and 4.5 titles
 Added ICX_PARAMETERS update in the Finishing tasks
July 23, 2004
 Section 2.2.a: specify to copy OA_JRE_TOP to cover cases when
the jre is not in COMMON_TOP/util
Jan 17, 2003  Initial Posting

Note 230672.1 by Oracle Applications Development

Copyright © 2009 Oracle Corporation
Last updated: January 22, 2008