8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 1/16

 Cloning Oracle Applications Release 11i with Rapid Clone [ID 230672.1] 

Modified 30-MAR-2011 Type WHITE PAPER Status PUBLISHED

View Change log 

Cloning Oracle Applications Release 11i 

with Rapid Clone

March 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 in document 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 TasksTasks 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 SystemApplications System being created as a copy of the

Source.

APPLMGR User which owns the Applications File System

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 2/16

(APPL_TOP and Application Tier technology stack)

ORACLEUser which owns the Database File System (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 Clonecustomers, 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.

SoftwareMinimum

VersionLocation Details

Oracle

Universal

Installer

2.2.0.19All Source

System Nodes

Apply OUI22 patch 5035661 on every iASand RDBMS ORACLE_HOME to be cloned.

Do not apply the patch to your RDBMS

ORACLE_HOME, if you have 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

MKSToolKit.

JRE 1.1.8Source

Database Node

If the RDBMS ORACLE_HOME was not

installed using Rapid Install, install JRE 1.1.8

into the [RDBMS ORACLE_HOME]/jre/1.1.8

directory.

JRE 1.3.1Source

Database Node

Windows users only: install JRE 1.3.1 into the

[RDBMS ORACLE_HOME]/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 11i on My Oracle

Support for instructions.

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 3/16

Zip2.3

(or higher)

All Source

Nodes

Download from InfoZip. Zip must be in your

PATH. If using files bigger than 2Gb, you

should use InfoZip ZIP 3.0 or higher.

UnZip5.52

(or higher)

All Source

Nodes

Download from InfoZip. UnZip must be in

your PATH. If using files bigger than 2Gb, you

should use InfoZip UNZIP 5.52 or higher.

OS utilities N/AAll 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.  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 VERSIONo  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

section Migrating 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_

the RDBMS ORACLE_HOME must be updated with the files included on those patches.

Follow the instructions in section Maintaining System Configuration in document 16

on My Oracle Support to synchronize the Rapid Clone and Autoconfig files on the RDBMS

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 4/16

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 

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 5/16

[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. Additiona

verify the permissions of the executables under ORACLE_HOME/bin that can potentially b

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 

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 6/16

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.

Table Name Column Name Column Value Details

WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE

Value starts with

http://[old web host] :

Update to new web host

WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE

Value starts with

"http://[old web host] :

Update to new web host

WF_SYSTEMS GUID

Create a new System

defined as the new global

Database name using the

Workflow AdministratorWeb 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_FUNCTIONS WEB_HOST_NAMEUpdate with the new web

host name

FND_FORM_FUNCTIONS WEB_AGENT_NAMEUpdate to point at the new

PLSQL listener name

FND_CONCURRENT_REQUESTS LOGFILE_NAME

Update with the correct

path to the logfile

directory

FND_CONCURRENT_REQUESTS OUTFILE_NAME

Update with the new

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 acceptabledirectory. 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 and

SESSION_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 

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 7/16

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 dbTi

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, theORACLE_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 ContextFile] 

Where Database Context File is:

[RDBMS ORACLE_HOME]/appsutil/[TargetCONTEXT_NAME].xml 

cd [COMMON_TOP]/clone/bin perl adcfgclone.pl appsTier [Appltop Target ContextFile] 

Where Appltop Context File is:[APPL_TOP]/admin/[Target CONTEXT_NAME].xml 

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 8/16

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.

f.  Perform prerequisites 

Perform these steps on all Source and Target Nodes.

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

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

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

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 9/16

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 

6. 

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.

7. 8.  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 aMulti-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 .

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

10. 

Note: For complete details on the certified RAC scenarios for E-Business Suite Cloning,

refer to Document 783188.1 available in My Oracle Support .

11.  To clone a RAC System, perform the following tasks:

.  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  

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

b. 

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 10/16

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

d.  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, runthe following command as the ORACLE File System owner:

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

e. 

f.  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 "Targetinstance is a Real Application Cluster (RAC) instance (y/n)", when prompted by

adcfgclone.pl.

12. 13.  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. 

14. 

Note: For complete details on the certified RAC scenarios for E-Business Suite Cloning,

refer to Document 783188.1 available in My Oracle Support .

15.  Perform the following tasks:

.  Choose any one of the ORACLE_HOMEs in the existing cluster and run the

following command:

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 11/16

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

16.  This ORACLE_HOME will be used as a master to create the additional Node(s).

.  Copy the master ORACLE_HOME File System to the new Node(s).

a.  On the init.ora, set the variable "cluster_Database_instances" to match the newnumber 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.

b. c.  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.

d. 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 [ContextFile] 

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 

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

.  Perform prerequisites 

Perform these steps on Node A and and every Target Nodes.

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 12/16

a.  Clone Oracle Applications 11i Perform a full clone (Prepare, copy and configure steps) of the Database Tier and

Node A (Application Tier).

b.  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 moreNodes 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: [RDBMSORACLE_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 fileswithin 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,

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 13/16

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 

Note 230672.1 by Oracle Applications Development

Copyright © 2010 Oracle Corporation

Last updated: March 30, 2010

Cloning Oracle Application 11i /R12 with Rapid Clone - Database (9i/10g/11g) Using Hot Backup onOpen Database [ID 760772.1] 

Modified 12-OCT-2010 Type HOWTO Status PUBLISHED

In this Document Goal 

Solution 

References 

Applies to:

Oracle Applications Manager - Version: 11.5.10.0 to 12.0.6 - Release: 11.5.10 to 12Information in this document applies to any platform.

Goal

This purpose of this article is to help to duplicate/clone the Active/Open database to another machine

Solution

You need following Cloning Note for your EBS Version

Release 11i : Note 230672.1 - 'Cloning Oracle Applications Release 11i with Rapid Clone' until 2.2asteps.Release 12 : Note 406982.1 - 'Cloning Oracle Applications Release 12 with Rapid Clone' until 2.2asteps.

This Note helps you to implement the steps mentioned in "Appendix B: Recreating database control files

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 14/16

manually in Rapid Clone" as per above Clone Note.

Step 1: Please run adpreclone If you have applied any patches to apps or dbif you havent applied any patches to apps or db , then you can skip adpreclone step.

Step 2: Obtain a trace file script to recreate the controlfile. On the source database issue the followingcommand:

SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE; 

The trace file script will be put into the user_dump_dest directory. The name of the trace file script will besomething like PROD_ora_12345.trc.Compare the date and time of the new trace file script to the time in which you entered the ALTERDATABASE BACKUP CONTROLFILE TO TRACE command.This will ensure you will be using the most recent trace file script, the one you created in this step

Step 3: In the create controlfile script just created in step 2 change:CREATE CONTROLFILE REUSE DATABASE "PROD" NORESETLOGS

to:

CREATE CONTROLFILE DATABASE "PROD" RESETLOGS ARCHIVELOG 

If you want to change the Database Name , You need to use the clause SET DATABASE <new dbname>in the create control file script as follows:

CREATE CONTROLFILE SET DATABASE "newdbname" RESETLOGS NOARCHIVELOG 

You must specify RESETLOGS.

The ARCHIVELOG mode may be changed to NOARCHIVELOG if you wish to run the copied database in

noarchive log mode. Change all directories in the create controlfile clause to point to the correctdirectories for the new target database, if necessary.

Leave "only" the CREATE CONTROLFILE clause. The other statements, like the recover command, willbe done manually. Be sure you also remove the STARTUP NOMOUNT command.

Note: Please ensure that there is no new datafile/tablespace added to Database after you generatecontrolfile script as above

Step 4: On the source database make an online copy of all datafiles using:

SQL> ALTER TABLESPACE <NAME> BEGIN BACKUP; 

Copy all datafiles within tablespace <NAME> to the new directory.On Unix systems, this can be done with the cp command.

Then do:

SQL> ALTER TABLESPACE <NAME> END BACKUP; 

Do NOT copy the controlfiles and redo log files as they will be recreated. You must copy the datafiles onlyafter the ALTER .. BEGIN BACKUP command has been executed, otherwise the datafiles may be

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 15/16

corrupted.

The names of the datafiles and tablespaces to which the datafiles belong can be obtained using thefollowing command:

SQL> SELECT FILE_NAME, TABLESPACE_NAME FROM DBA_DATA_FILES; 

Note: Instead of performing step 4 and step 5 to create a new online backup, you may instead use apreviously taken online backup of your database.If you choose to use a previous online backup be sure tocopy the required archived redo logs taken with the the previous online backup.

Step 5: After all datafiles have been copied and the tablespaces taken out of backup mode issue thefollowing command:

SQL> ALTER SYSTEM ARCHIVE LOG CURRENT; 

You will need all of the archivelog files from the start of datafile copy commands including the one justcreated with the command ALTER SYSTEM ARCHIVE LOG CURRENT.

Step 6: Copy the database (DBF) files,controlfile script and archive log files from the source to the target

system

Step 7: So, As mentioned in 230672.1 (Appendix B), Replace section 2.2a (Configure the target systemdatabase server) with the following steps:

Execute the following commands to configure the target system. You will be prompted for the targetsystem specific values (SID, Paths, Ports, etc)

Log on to the target system as the ORACLE user

Configure the <RDBMS ORACLE_HOME>

cd <RDBMS ORACLE_HOME>/appsutil/clone/binperl adcfgclone.pl dbTechStack 

Step 7: On the target system issue STARTUP NOMOUNT command. For example:

SQL> startup nomount pfile=initTEST.ora 

Step 8: Run the prepared script created in step 3 to create the new controlfile. For example:

SQL> @PROD_ora_12345.trc 

Step 9: Issue the command:

SQL> RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE

You will be prompted to apply all of the archived redo logs from the source database includingthe last archive redo log file created with the ALTER DATABASE ARCHIVE LOG CURRENTcommand from step 5.

After applying all of these archive log files issue the CANCEL command.

8/7/2019 HotCloning OraApps11i

http://slidepdf.com/reader/full/hotcloning-oraapps11i 16/16

Step 10: Open the database with resetlogs:

SQL>ALTER DATABASE OPEN RESETLOGS 

At this point the target database will have been successfully cloned and opened.

Step 11: Create Temporary Tablespace if not created in Source, else you shall add Temporarytablespace

You can check if tablespace TEMP has tempfiles or datafiles using the following SQL:

SQL> SELECT FILE_NAME,TABLESPACE_NAME,STATUS,AUTOEXTENSIBLE from DBA_TEMP_FILES whereTABLESPACE_NAME like 'TEMP';

SQL> SELECT FILE_NAME,TABLESPACE_NAME, STATUS,AUTOEXTENSIBLE FROM DBA_DATA_FILES WHERETABLESPACE_NAME LIKE 'TEMP'; 

If Temporary Tablespace is not created from above query,SQL> create temporary tablespace temp add tempfile 'xxxx.dbf' size xx 

Or

SQL> alter tablespace TEMP add tempfile 'xxxx.dbf' size xx 

Step 12: Run the library update script against the database

cd <RDBMS ORACLE_HOME>/appsutil/install/<CONTEXT NAME> 

sqlplus "/ as sysdba" @adupdlib.sql <libext>

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

Step 13: 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

Please follow the remaining steps as per Cloning for your EBS version :Release 11i : Note 230672.1 - 'Cloning Oracle Applications Release 11i with Rapid Clone'Release 12 : Note 406982.1 - 'Cloning Oracle Applications Release 12 with Rapid Clone'

References

NOTE:230672.1 - Cloning Oracle Applications Release 11i with Rapid CloneNOTE:406982.1 - Cloning Oracle Applications Release 12 with Rapid Clone