Cloning Oracle Applications Release 11i with Rapid Clone [ID 230672.

1]

  Modified 05-APR-2011     Type WHITE  
PAPER     Status PUBLISHED
  View Change log

Cloning Oracle Applications Release 11i 

with Rapid Clone
April 2011

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 My
Oracle Support. A FAQ is also available indocument 216664.1 on My Oracle
Support.

  Note: Rapid Clone is currently not supported on HP OpenVMS Alpha.

Attention: Windows users. This document typically uses UNIX syntax
when specifying directories; Please substitute the appropriate Windows
syntax
Note: The Cloning methodology posted on this document requires full
Autoconfig complience.

 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.
User which owns the Applications File
APPLMGR 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 brackets represents a
[] variable. Substitute a value for the variable
text. Do not type the brackets.

Section 1: Prerequisites

Before cloning, prepare the Source System by applying patches and running
AutoConfig.

1. Verify Source and Target Nodes software versions

In addition to the Oracle Applications software requirements (see the
Oracle Applications Release Notes and the Oracle
Applications Installation Update Notes for your Platform), 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.
Minimum
Software Location Details
Version

Apply OUI22 patch 5035661 on

every iAS and RDBMS
Oracle All Source ORACLE_HOME to be cloned.
Universal 2.2.0.19 System Do not apply the patch to your
Installer Nodes RDBMS ORACLE_HOME, if you
have Oracle 10g or higher
installed.
 Use the Perl shipped with iAS1022
Source and and RDBMS 9i if available or
Target download it from Perl.com. Perl
Perl 5.005
Database must be in the PATH before
Nodes cloning. Windows users: do not
use Perl from MKSToolKit.
If the RDBMS ORACLE_HOME
was not installed using Rapid
Source
Install, install JRE 1.1.8 into the
JRE 1.1.8 Database
[RDBMS
Node
ORACLE_HOME]/jre/1.1.8
directory.
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. SeeAppendix A for
installation instructions.
Target Refer to Upgrading to JDK 1.3
middle-Tier with Oracle Applications 11i
JDK 1.3.1
Applications on My Oracle Support for
Nodes instructions.
Download from InfoZip. Zip must
2.3  All Source be in your PATH. If using files
Zip
(or higher) Nodes bigger than 2Gb, you should use
InfoZip ZIP 3.0 or higher.
Download from InfoZip. UnZip
5.52  All Source must be in your PATH. If using
UnZip
(or higher) Nodes files bigger than 2Gb, you should
use InfoZip UNZIP 5.52 or higher.
OS utilities (see 11i Install
Manual) must be in the the PATH
OS All Target
N/A when running adcfgclone.pl (Unix:
utilities Nodes
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.
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 My Oracle Support 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 9171650 : 11i RAPIDCLONE CONSOLIDATED FIXES
JUL/2010
o 9874305 : ADMKAPPSUTIL.PL COMPLAINS ABOUT UNZIP
VERSION
o 10182813 : Required if using 11gR2 version of the Database
o 8977646 : Required for Windows Platforms
6. Setup Rapid Clone on the Applications Tier
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 My Oracle Support). 
All users must run AutoConfig on the Applications Tier (see section
5: Maintaining System Configuration in document 165195.1 on My
Oracle Support).
7. Setup Rapid Clone on the Database Tier
Implement AutoConfig in the RDBMS ORACLE_HOME (Follow the
instructions in sectionMigrating to AutoConfig on the Database Tier in
document 165195.1 on My Oracle Support).
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.
8.
9. 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 commands:

cd [RDBMS
ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
perl adpreclone.pl 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 adpreclone.pl 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 user.
 Shut down the Application Tier Server processes
 Copy the following Application Tier directories from the
Source Node to the Target Application Tier Node: 

[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]

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

Database
 Copy the Database (DBF) files from the Source to the
 Target System
 Copy the Source Database ORACLE_HOME to the
Target System
 Start up the Source Applications System Database and
Application Tier processes

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).
3.
4. 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 adcfgclone.pl 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 adcfgclone.pl appsTier

Attention: Windows users 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
Details
Value starts with
http://[old web host] :
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE
Update to new web
host
Value starts with
"http://[old web host] :
WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE
Update to new web
host
Create a new System
defined as the new
global Database name
WF_SYSTEMS GUID using the Workflow
Administrator Web
Applications
responsibility.
Value needs to be
WF_SYSTEMS NAME replaced with the
Database global name
Update Database link
WF_AGENTS ADDRESS with the new Database
global name.
Update with the new
FND_FORM_FUNCTIONS WEB_HOST_NAME
web host name
Update to point at the
FND_FORM_FUNCTIONS WEB_AGENT_NAME new PLSQL listener
name
Update with the
FND_CONCURRENT_REQUESTS LOGFILE_NAME correct path to the
logfile directory
Update with the new
FND_CONCURRENT_REQUESTS OUTFILE_NAME directory path on the
Target System
4.
5. 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.
6. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the Target System is in a different domain name than the Source
System andSESSION_COOKIE_DOMAIN was not null in the Source
System, update that value to reflect the new domain name.
7. Re-Implement SSL and SSO configuration
 If the Source System was SSL or SSO enabled, reconfigure the Target by
following the SSL/SSO documentation.
8. 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 time.
c. Configure the Target System
Specify the existing Target System Context File when running
adcfgclone.pl commands:

cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier [Database Target Context
File]

Where Database Context File is:

[RDBMS ORACLE_HOME]/appsutil/[Target
CONTEXT_NAME].xml
 cd [COMMON_TOP]/clone/bin
perl adcfgclone.pl 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 My
Oracle Support 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
System.

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 adcfgclone.pl completes, Source the Applications
environment and run the following commands on the Target
System:

cd [COMMON_TOP]/clone/bin
perl adaddNode.pl

3.
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.
4.
5. Reducing the number of Nodes of a Multi-Node System (merge
APPL_TOP)
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.
6. 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.
Attention: The following steps apply only for 9i RAC Clusters. For 10g
or 11g RAC environments, please follow the instructions in
Document 760637.1.
7.
Note: For complete details on the certified RAC scenarios for E-
Business Suite Cloning, refer to Document 783188.1 available in My
Oracle Support.
8. 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 My
Oracle Support
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 adpreclone.pl
dbTier" on it. 
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.
c.
d. 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. 
e. Configure the Target System
o Log on to any ORACLE_HOME in the Target cluster and
run

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.

o For each remaning RDBMS ORACLE_HOME in the

Target System, run the following command as the
ORACLE File System owner:

cd [RDBMS
ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier

f.
g. 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 adcfgclone.pl.
9.

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.
6.
Note: For complete details on the certified RAC scenarios for E-
Business Suite Cloning, refer to Document 783188.1 available in My
Oracle Support.
7. Perform the following tasks:

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

8. This ORACLE_HOME will be used as a master to create the

additional Node(s).

i. Copy the master ORACLE_HOME File System to the new

Node(s).
 j. 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.
k.
l. 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 [RDBMS
ORACLE_HOME]/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.
m.
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 [RDBMS
ORACLE_HOME]/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 [RDBMS
ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier

9. 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:

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 My
Oracle Support 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
location: [RDBMS ORACLE_HOME]\jre\1.3.1
 Accept the default installation options.

JRE 1.3.1 will be installed into the [RDBMS ORACLE_HOME]\jre\1.3.1

directory.

Appendix B: Recreating Database control files manually in Rapid Clone.

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:

 Log on to the Target System as the ORACLE user

 Configure the [RDBMS ORACLE_HOME>

cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTechStack
  Create the Target Database control files manually

 Start the Target System Database in open mode

 Run the library update script against the Database

cd [RDBMS ORACLE_HOME]/appsutil/install/[CONTEXT
NAME]
sqlplus "/ as sysdba" @adupdlib.sql [libext]

Where [libext] should be set to 'sl' for HP-UX, 'so' for any other
UNIX platform, 
or 'dll' for Windows.

 Configure the Target Database (the Database must be open)

cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbconfig [Target Context File]

Where Target Context File is:

[RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml 

Change Log
Date Description
April 05, 2011  Corrected Hyperlink on some patches
 Added a note for Autoconfig requirement.
 Corrected links in patches
March 30, 2011
 Added Patch 9874305.
 Added Patch 10182813 required if using 11gR2 Database
November 04,
2010
 Added more explicit clarification to review Release Notes and Installation Update N
September 28,
 Corrected RC Patch label with correct month
2010
September 24,
 Replaced RC Consolidated Patch with 9171650
2010
April 24, 2010  Added Patch 9504918
February 15,  Addressed general formating issues
2010  Replaced Rapid Clone Consolidated Patch with 8360498 (JAN/2010)
 Removed other patches since they are now included in 8360498
 Removed Windows Itanium desupport notice
 Added clarifications for versions of ZIP and UNZIP in Section 1
  Added additional step for SSL/SSO in Section 3

 Changed references from OracleMetalink to My Oracle Support

June 29, 2009  Addressed general formating issues
May 08, 2009  Replaced Rapid Clone Consolidated Patch with 7164202 (MAY/2009)
April 08, 2009  Added reference to Note 760637.1 for 10g/11g RAC Cloning
March 02, 2009  Added reference to Note 783188.1 for RAC Cloning
 Added Patch 8217144 for Windows Platforms
February 12,
2009
 Added Patch 8251658 for Windows Platforms
 Added 11i/10g/11g RAC clarification on Section 4 Steps 6 and 7.
February 04,
2009
 Corrected incorrect format statements
 Removed Unsupported statement for Windows x86-64 (EM64T) and updated the pl
January 22, 2009
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)
 Removed Patch 6913832 since its included on 6718351 (JUL/2008)
August 07, 2008
 Removed Patch 6438830 since its included on TXK.S (6372396) now released in M
March 26, 2008  Added Patch 6913832 required for HP-UX PA-RISC 64-bit and 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
December 17,
 Added clarification to backup the Context File when refreshing a Target System on
2007
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 Rapid Clone or
March 26, 2007
Autoconfig
March 25, 2007  Added a step to apply the latest Minipack for AD
January 08, 2007  Removed HP Tru64 desupport note since the issues have been fixed on TXK-O
December 04,
 Added HP OpenVMS Alpha and HP Tru64 as non Supported Platforms
2006
August 16, 2006  Added Windows x86-64 (AMD64/EM64T) as non Supported Platform
  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
May 9, 2006  Added TXK Autoconfig Template RollUp Patch in the prereq 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 APPL_TOP System
March 09, 2005
 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,  Added instructions for RAC cloning (Section 4.6)
2004
 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

Note 230672.1 by Oracle Applications Development

Copyright © 2010 Oracle Corporation
Last updated: April 05, 2010

 Related
Products

 Oracle E-Business Suite > Applications Technology > Lifecycle Management >
Oracle Applications Manager

Keywords

ORACLE UNIVERSAL INSTALLER 2 2

Back to top

Rate this document