cloning apps

8/9/2019 Cloning Apps

1/15

Cloning Oracle Applications Release 11i

with Rapid Clone

August 2006

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

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

on Windows x86-64 (AMD64/EM64T).

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.

Conventions

Convention Meaning

Source system Applications system being cloned.

Target system Applications system being created as acopy of the source.

APPLMGR

User which owns the applications file

system (APPL_TOP and application tier

technology stack)

ORACLE User which owns the database file system

(RDBMS ORACLE_HOME and database
http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=230672.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=216664.1https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prereq%23prereqhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#manual%23manualhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#options%23optionshttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=230672.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=216664.1https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prereq%23prereqhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#manual%23manualhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#options%23options


2/15

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

. For new AutoConfig or Rapid Clonecustomers, CONTEXT_NAME will be set to

_.

Monospace TextRepresents 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.

1. Verify source and target nodes software versionsIn addition to the Oracle Applications software requirements (see InstallingOracle Applications Release 11i Part No. B10638-01), the following softwarecomponent versions must exist on the source and/or target nodes. Thelocation column indicates the node where the software component must be

present.

Softwar

e

Minimu

m

Version

Location Details

Oracle

Universal

Installer

2.2.0.19

All source

system

nodes

Apply OUI22 patch 5035661 on every

iAS and RDBMS ORACLE_HOME to be

cloned. Do not apply the patch to

your RDBMS ORACLE_HOME, if youhave Oracle 10g or higher installed.

Perl 5.005 Source and

target

database

nodes

Use the Perl shipped with iAS1022

and RDBMS 9i if available or

download it from Perl.com. Perl must

be in the PATH before cloning.

Windows users: do not use Perl from
http://updates.oracle.com/ARULink/PatchSearch/process_form?bug=5035661&language=0&process=Submithttp://www.perl.com/pub/a/language/info/software.htmlhttp://updates.oracle.com/ARULink/PatchSearch/process_form?bug=5035661&language=0&process=Submithttp://www.perl.com/pub/a/language/info/software.html


3/15

MKSToolKit.

JRE 1.1.8

Source

database

node

If the RDBMS ORACLE_HOME was not

installed using Rapid Install, install

JRE 1.1.8 into the /jre/1.1.8 directory.

JRE 1.3.1

Source

database

node

Windows users only: install JRE 1.3.1

into the /jre/1.3.1 directory.

See Appendix A for installation

instructions.

JDK 1.3.1

Target

middle-tier

applications

nodes

Refer to Upgrading to JDK 1.3 with Oracle

Applications 11ion OracleMetaLinkfor

instructions.

Zip 2.3All source

nodes

Download from InfoZip. Zip must be in

your PATH for cloning.

OS

utilitiesN/A

All target

nodes

OS utilities (see 11i Install Manual)

must be in the the PATH when

running adcfgclone.pl (Unix:

make,ld,cc,ar - Windows:

gnumake,link,cc,cmd)

2. Windows users only:Apply patch 2237858 to enable long file names support.

3. Apply the latest AutoConfig Template patchUpdate the Oracle Applications file system with the latest AutoConfigtemplate files by applying the TXK AutoConfig Template rollup patch to allapplication tier server nodes.Please refer to document 165195.1 on OracleMetaLinkto obtain the latestAutoconfig165195.1 on OracleMetaLinkto obtain the latest AutoconfigTemplate Rollup Patch available in Metalink.

4. Apply the latest Rapid Clone patchesUpdate 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 5225940 (Post ADX.F Fixes)

5. Setup Rapid Clone on the Applications Tier

a. If the source Applications system was created with Rapid Installversion 11.5.5 or earlier and has not been migrated to AutoConfig,follow the instructions Migrating to AutoConfig on the Applications Tier
https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#appendixA%23appendixAhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=130091.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=130091.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=130091.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=130091.1http://www.info-zip.org/http://updates.oracle.com/ARULink/PatchSearch/process_form?bug=2237858&language=0&process=Submithttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#maintainhttp://updates.oracle.com/ARULink/PatchSearch/process_form?bug=3453499&language=0&process=Submithttp://updates.oracle.com/ARULink/PatchSearch/process_form?bug=5225940&language=0&process=Submithttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#implementhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#appendixA%23appendixAhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=130091.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=130091.1http://www.info-zip.org/http://updates.oracle.com/ARULink/PatchSearch/process_form?bug=2237858&language=0&process=Submithttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#maintainhttp://updates.oracle.com/ARULink/PatchSearch/process_form?bug=3453499&language=0&process=Submithttp://updates.oracle.com/ARULink/PatchSearch/process_form?bug=5225940&language=0&process=Submithttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#implement


4/15

Migrating to AutoConfig on the Applications Tierin document165195.1 on OracleMetaLink).

b. All users must run AutoConfig on the Applications Tier (see section 5:Maintaining System ConfigurationMaintaining System Configuration in document165195.1 on OracleMetaLink).

2. Setup Rapid Clone on the Database Tier

Implement AutoConfig in the RDBMS ORACLE_HOME (Follow the instructionsin section Migrating to AutoConfig on the Database TierMigrating to AutoConfig onthe Database Tierin document 165195.1 on OracleMetaLink). Follow steps 1and 4 of Section 7 in the AutoConfig document for all versions ofRapidInstall and every time you apply a new version of the Rapid Clonepatch.

3. Maintain Snapshot informationLog in to each Application Tier Node as the APPLMGR user and run MaintainSnapshot 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 SystemExecute the following commands to prepare the source system for cloning.

a. Prepare the source system database tier for cloningLog on to the source system as the ORACLE user and run the followingcommands: cd /appsutil/scripts/ perl adpreclone.pl dbTier

b. Prepare the source system application tier for cloningLog on to the source system as the APPLMGR user and run thefollowing commands on each node that contains an APPL_TOP: cd /admin/scripts/ perl adpreclone.pl appsTier

2. Copy the Source System to the Target System

Copy the application tier file system from the source Applications system tothe target node by executing the following steps in the order listed. Ensurethe application tier files copied to the target system are owned by thetarget APPLMGR user, and that the database tier files are owned by theORACLE user.

a. Copy the application tier file systemLog on to the source system application tier nodes as the APPLMGRuser.

Shut down the application tier server processes
http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#maintainhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#implement-dbhttp://download-west.oracle.com/docs/cd/B15436_01/current/acrobat/11iadutil.pdfhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#maintainhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1#implement-dbhttp://download-west.oracle.com/docs/cd/B15436_01/current/acrobat/11iadutil.pdf


5/15

Copy the following application tier directories from the sourcenode to the target application tier node:

/util /clone /_pages (when this directory exists)

b. Copy the database tier file systemLog 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 andapplication tier processesNote: Unix/Linux users, make sure that the softlinks are preserved when

copying.

3. Configure the Target SystemExecute the following commands to configure the target system. You will beprompted for the target system specific values (SID, Paths, Ports, etc)

a. Configure the target system database serverLog on to the target system as the ORACLE user and type thefollowing commands to configure and start the database:

cd /appsutil/clone/bin perl adcfgclone.pl dbTierb. Configure the target system application tier server nodes

Log on to the target system as the APPLMGR user and type thefollowing commands: cd /clone/bin perl adcfgclone.pl appsTier

Attention: Windows user only: add \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 optionsRapid Clone updates only site level profile options. If any other profileoptions are set to instance specific values, you must update them manually.


6/15

2. Update printer settingsIf the new cloned system needs to utilize different printers, update thetarget system with the new printer settings now.

3. Update workflow configuration settingsCloning an Oracle Applications instance will not update the host andinstance specific information used by Oracle Workflow. Review the following

tables and columns to verify there is no instance specific data in theWorkflow configuration on the target system.Table Name Column Name Column Value Details

WF_NOTIFICATION_ATTRIB

UTESTEXT_VALUE

Value starts with http:// : Update to new

web host

WF_ITEM_ATTRIBUTE_VAL

UESTEXT_VALUE

Value starts with

"http:// :

Update to new web host

WF_SYSTEMS GUID

Create a new system

defined as the new global

database name using the

Workflow Administrator

Web Applications

responsibility.

WF_SYSTEMS NAME

Value needs to be replaced

with the database global

name

WF_AGENTS ADDRESS

Update database link with

the new database global

name.

FND_FORM_FUNCTIONSWEB_HOST_NA

ME

Update with the new web

host name

FND_FORM_FUNCTIONSWEB_AGENT_NA

ME

Update to point at the new

PLSQL listener name

FND_CONCURRENT_REQU

ESTSLOGFILE_NAME

Update with the correct

path to the logfile directory

FND_CONCURRENT_REQU

ESTSOUTFILE_NAME

Update with the new

directory path on the target

system


7/15

4. Verify the APPLCSF variable settingSource the APPS environment and review that the variable APPLCSF(identifying the top-level directory for concurrent manager log and outputfiles) points to an acceptable directory. To modify it, change the value ofs_applcsfin the contextfile and run AutoConfig.

5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS

If the target system is in a different domain name than the source systemand SESSION_COOKIE_DOMAIN was not null in the source system, updatethat value to reflect the new domain name.

6. Windows users only reboot the target machineOnce 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 itwith changes from the source.

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, 806ORACLE_HOME, or iAS ORACLE_HOME needs to be refreshed.Copy the portion of the application tier file system which hasbeen updated.

o Copy the database tier file system if the RDBMS ORACLE_HOMEor the database needs to be refreshed. If refreshing thedatabase, the ORACLE_HOME should be refreshed at the sametime.

c. Configure the Target System

Specify the existing target system context file when runningadcfgclone.pl commands:

o perl adcfgclone.pl dbTier

where database context file is: /appsutil/.xml

o perl adcfgclone.pl appsTier

where appltop context file is: /admin/.xml

d. Finishing Tasks

2. Cloning a single-node system to a multi-node systemThis procedure allows the original single-node system to be cloned into amulti-node system. An Applications system comprises five server types:

o Database server (database tier)o Forms server (application tier)
https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prepare%23preparehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#copy%23copyhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#configure%23configurehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#manual%23manualhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prepare%23preparehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#copy%23copyhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#configure%23configurehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#manual%23manual


8/15

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. Whencreating more than one application tier server node from a singlenode system, the copy and configure steps must be performed oneach target node. You can specify the server type for each targetnode while answering the prompts during the configuration step.The database ORACLE_HOME and database only need to be copied tothe 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

OracleMetaLinkdocument 233428.1 on OracleMetaLinkfor details.

3. Cloning a multi-node system to a multi-node system with samenumber of nodesA multi-node system can be cloned provided the number of nodes anddistribution of servers in the target system matches that of the sourcesystem.

To clone a multi-node system to a multi-node system, perform the cloning process on eachnode. 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 existingApplication System. The new node will run the same or a subset of theserver types running on the source node. Follow the instructions in theApplication Tier part ofClone 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:o cd /clone/bino perl adaddnode.pl
https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prereq%23prereqhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#manual%23manualhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prereq%23prereqhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#manual%23manualhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clone


9/15

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 HostsManaged SQL*Net Access from Hosts in

document 281758.1 on OracleMetalinkfor instructions on how to

achieve this from OAM.

3. Reducing the number of nodes of a multi-node system (mergeAPPL_TOP)You can use Rapid Clone to clone a multi-node system to a single-nodesystem (or a multi-node system with fewer nodes) by merging theAPPL_TOPs filesystem together. Follow the procedure for Merging existingAPPL_TOPs in document 233428.1 Merging existing APPL_TOPs in document233428.1 on OracleMetaLink.

4. Cloning a RAC systemYou can use Rapid Clone to clone a RAC system. While cloning, you have thepossibility 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 prerequisiteso 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 onOracleMetaLinkdocument 165195.1 on OracleMetaLink

b. Prepare the Source System

Choose one of the ORACLE_HOMEs on the source cluster. ThisORACLE_HOME will be used as a master to create all the target clustersystem 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. Copy the Source System to the Target System

o Copy the master ORACLE_HOME from the source system to eachnode that will compose the target cluster. For example, if yoursource RAC system had 2 nodes, and you want to clone it to a 3node target RAC system, you should copy the source masterORACLE_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 run 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
http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=281758.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=281758.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#mergehttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#mergehttp://updates.oracle.com/ARULink/PatchSearch/process_form?bug=3571388&language=0&process=Submithttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prepare%23preparehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#copy%23copyhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#configure%23configurehttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=281758.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=281758.1http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#mergehttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#mergehttp://updates.oracle.com/ARULink/PatchSearch/process_form?bug=3571388&language=0&process=Submithttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=165195.1https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prepare%23preparehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#copy%23copyhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#configure%23configure


10/15

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:

adcfgclone.pl dbTier

o If your database is version 10g or higher, run the followingcommands to register the database and the instance to thecluster manager .

srvctl add database -d -o srvctl add instance -d \

-i -n 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 adcfgclone.pl

e. Clone the application tier

Follow the steps in section 2 to prepare, copy and configure theapplication tier. When prompted for the database SID, specify any oneof 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.

4. Adding a node to an existing RAC ClusterYou 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 adpreclone.pl dbTier" on it. This ORACLE_HOME will be used as amaster to create the additional node(s).

g. Copy the master ORACLE_HOME filesystem to the new node(s).h. 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 addingmore 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 nodefrom the original cluster and run the following command oneach of them:

cd /appsutil/clone/bin
https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clone


11/15

perl adcfgclone.pl addracnode o Go back to the first node and complete adcfgclone.plo 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

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 adcfgclone.pl

5. Cloning a Shared File SystemYou can use Rapid Clone to clone a shared APPL_TOP system. Since all thenodes share a unique APPL_TOP you only need to fully clone one of thesource system nodes to its target machine and add more nodes directlysharing the APPL_TOP on the target system. Choose one of the sharedAPPL_TOP nodes on source system (the rest of this section will refer to it as

Node A) and perform the following tasks:

i. Perform prerequisitesPerform these steps on Node A and and every target nodes.

j. Clone Oracle Applications 11iPerform a full clone (Prepare, copy and configure steps) of theDatabase Tier and Node A (Application tier).

k. Add the shared file system nodes to the target systemOn the target system, follow the instructions for adding a node to a sharedAPPL_TOP system in document 233428.1adding a node to a sharedAPPL_TOP system in document 233428.1 on OracleMetalinkand add

more nodes sharing the target system APPL_TOP to match the sourcesystem 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:\jre\1.3.1

Accept the default installation options.

JRE 1.3.1 will be installed into the \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
https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prereq%23prereqhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#addhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#addhttp://java.sun.com/https://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#prereq%23prereqhttps://metalink.oracle.com/metalink/plsql/f?p=130:14:10853368068711460783::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,230672.1,1,1,1,helvetica#clone%23clonehttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#addhttp://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=233428.1#addhttp://java.sun.com/


12/15

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

o cd /appsutil/clone/bino

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

o cd /appsutil/install/o sqlplus "/ as sysdba" @adupdlib.sql

where is "sl" for HP-UX, "so" for any other UNIX platform andnot required for Windows.

Configure the target database (the database must be open)o cd /appsutil/clone/bino perl adcfgclone.pl dbconfig

where target context file is:

/appsutil/.xml

MULTI NOD ETO SINGLE NOD E CLONING

Multi Node to Single Node Cloning

With Oracle Applications 11.5.10 the ability to clone from a multi node to a single node system usingrapid clone has now been certified.

This is accomplished by the Shared APPL_TOP and Merging APPL_TOP features.

In this post i am listing out the steps to perform a multi note to a single node cloning from scratch. The

information mentioned here is the steps which i have used and found them to be successful for a more

elaborate explanation you might want to refer to the metalink note Sharing the Application Tier FileSystem in Oracle E-Business Suite 11i (233428.1).

Source System here refers to the multi node system to be cloned

Target System refers to the newly to be created single node system

Applications Version 11.5.10

Operating System Linux ES 4

The following Steps are required to be performed on the source system

1.Apply application tier patches using adpatch


13/15

Apply patch 4038964

Apply patch 4175764

Both the above patches are include in the consolidated update 2 or CU2 so in case you are on 11.5.10.2

or later you can ignore this step.

2. Maintain snapshot information

Log in as the applications user on each application tier node and run 'Maintain Snapshot Information'by using adadmin.

3. Merge existing APPL_TOPs

Log in to the primary node of your application tier as the application user user and run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]$ perl adpreclone.pl appsTier merge

This will prompt you with option to merge secondary nodes

Now log in as the applications user to each of the secondary application tier nodes being merged and

run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]$ perl adpreclone.pl appltop merge

4. Prepare the source system database tier.

Log on to the database tier of the source system as the oracle user and run the following commands:

$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]$ perl adpreclone.pl dbTier

With this all the pre clone tasks on the source system have been completed.

The next set of tasks are required to be carried out on the target system that is the system on which youwish to place the merged single node instance.

1. Create OS user accounts

Create a OS user account for your applications

$ useradd -g dba -d [home_directory] -p password username

Similarly create a OS user account for your database

2. Modify the orainventory to reflect the new location

$ vi /etc/oraInst.loc

3. Copy the following application tier directories

Copy the following application tier directories from the primary node of your source system to the

target application tier node, retaining the original directory structure:

[APPL_TOP] [OA_HTML] [OA_JAVA] [COMMON_TOP/util]


14/15

[COMMON_TOP/clone> [806 ORACLE_HOME] [iAS ORACLE_HOME]

4. Copy the required files for merging

Log in as the applications user to each of the secondary source nodes and recursively copy:

directory [COMMON_TOP]/clone/appl- to -directory [COMMMON_TOP]/clone/applon the target system node

Before proceeding with the next steps you must shutdown your oracle applications services and the

database on the source system

5. Copy the database tier file system

Log on to the source system as the database user

Copy the database (DBF) files from the source to the target systemCopy the source database ORACLE_HOME to the target system

After this you can now startup the database and applications services on your source system and release

it for use.

6. Configure the target system database server

Log on to the target system as the database user and type the following commands to configure and

start the database:

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

This will prompt for new ORACLE_SID,ORACLE_HOME,Port Pool,JAVA_TOP and DATA_TOP

give the appropriate values matching your target system

Once successful this should start your database and listener

7. Configure the application tier server nodes

The database and its listener should remain up before executing the next set of commands.

Log in to the merged APPL_TOP node as the applications user and execute the following commands:

$ cd [COMMON_TOP]/clone/bin$ perl adcfgclone.pl appsTier

This will prompt you new port pool for applictaion tier services as well as new

APPLTOP,COMMON_TOP,ORACLE_HOME and IAS_TOPSuccessful completion of this task will bring up your application tier services on the target or the

cloned node.

8. Post Clone Tasks

Log in to the target system application tier node as the APPLMGR user.Run the following tasks in adadmin for all products:

o generate JAR fileso generate message files


15/15

o relink executableso copy files to destination

9. Clean up of the target system

Remove the temporary directory [COMMON_TOP]/clone/applto reduce disk space usage.

Note: The version of Oracle Applications used is 11.5.10 and the operating system is Linux ES 4

cloning apps

Documents