Escolar Documentos
Profissional Documentos
Cultura Documentos
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 OracleMetaLink.
A FAQ is also available in document 216664.1 on OracleMetaLink.
• 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.
Applications system being created as a copy of the
Target system
source.
User which owns the applications file system
APPLMGR (APPL_TOP and application tier technology
stack)
User which owns the database file system
ORACLE
(RDBMS ORACLE_HOME and database files).
CONTEXT_NAME 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
<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 AutoConfig.
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
OracleMetaLink).
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.
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.
This section lists tasks that may be necessary depending on your implementation and the
intended use of the cloned system.
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
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.
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.
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.
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 OracleMetaLink.
7. Perform the following tasks:
i. Choose any one of the ORACLE_HOMEs in the existing cluster and run
"perl adpreclone.pl dbTier" on it. This ORACLE_HOME will be used as a
master to create the additional node(s).
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.
l.
m. 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 adcfgclone.pl 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 adcfgclone.pl
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 adcfgclone.pl addracnode <context file>
o Go back to the first node and complete adcfgclone.pl
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 adcfgclone.pl dbTier
n. Perform prerequisites
Perform these steps on Node A and and every target nodes.
o. Clone Oracle Applications 11i
Perform a full clone (Prepare, copy and configure steps) of the Database
Tier and Node A (Application tier).
p. 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.
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 steps: