Escolar Documentos
Profissional Documentos
Cultura Documentos
Rapid Clone
Doc ID: 230672.1 Type: WHITE PAPER
Modified Date : 22-JAN-2009 Status: PUBLISHED
View Change log
• 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
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
ORACLE (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
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
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.
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. 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
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:
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
Standards.
October 16, 2008 Added Required Patches for Windows 32 Bit and AM64
Replaced Rapid Clone Consolidated Patch with 6718351
(JUL/2008)
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
Platforms.
Added Windows x86-64 (AMD64/EM64T) as non Supported
Platform.
August 16, 2006 Modified Section 1, Step 6 to point to correct Section on Document
165195.1
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
section.
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 adcfgclone.pl 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
exists
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