Subject: Cloning Oracle Applications Release 11i with Rapid Clone
Doc ID: NOTE:230672.1
Type: WHITE PAPER
Last Revision Date: 07-AUG-2008
View Change log
Cloning Oracle Applications Release 11i
with Rapid Clone
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 OracleMetaLink.
Note: Rapid Clone is currently not supported on Windows Itanium, Windows x86-64
(AMD64/EM64T) and HP OpenVMS Alpha.
Attention: Windows users. This document typically uses UNIX syntax when specifying
directories; Please substitute the appropriate Windows syntax
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.
Applications system being cloned.
Applications system being created as a copy of the
User which owns the applications file system
(APPL_TOP and application tier technology stack)
User which owns the database file system (RDBMS
ORACLE_HOME and 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 typically be
set to <SID>. For new AutoConfig or Rapid Clone
customers, CONTEXT_NAME will be set to