cloning single to multi

8/6/2019 Cloning Single to Multi

http://slidepdf.com/reader/full/cloning-single-to-multi 1/21

Author – A.Kishore/Sachin

http://appsdba.info

1

Cloning a Single-Node System To a Multi-Node System

Introduction

This document describes a step-by-step approach for cloning an Oracle Applications 11i whic

AutoConfig enabled using Rapid Clone from one to three nodes, it includes Port Selection, Fo

Server, Reports Server, Apache Server and Concurrent Processing, also all the scripts or progr

which are used to startup up and shutdown all the services. The cloning word means to do a functio

copy of an existing environment. Simply copying the application directories doesn’t mean that our environment will work properly, we need to do some additional steps or tasks to have a functio

environment.

CLONE – Single Server to Two Node Server

SOURCE Server – PROD

DB Tierprodb

proddata

Apps Tier

prodcomn

prodappl

prodora

TARGET Server – DEV

DB Tierdevdb

devdata

TARGET Server – DEV

Apps Tier

devcomn

devappl

devora




http://appsdba.info

2

Some of the reasons to do a cloning are:

• To create a test environment from an existing production environment to test some patches o

reproduce any production issues.

• To keep a test environment with the most current information of a production environment.

• To move any existing environment to other servers.

In this Cloning demonstration, we will clone our single node instance “PROD” to Two-node as one n

for database server and second node is for Application. That means all application services will reon one node and database on a separate node. Our source node is ERP and target node is also E

And our source database node is PROD and Target database node is DEV. The TARGET direc

structure of both the node is same as Source that is /d01/oracle.

Cloning prerequisite steps:

We should remember that the clone application system and existing Production application syst

must have same component versions & operating system type. And also we cannot clone fr

windows to linux.

Login as Applications file user & set the environment file on source node.

su applmgr

cd /d01/oracle/prodappl

. ./APPSORA.env




http://appsdba.info

3

Login to database tier as oracle user and set the environment on source node.

su oracle

cd /d01/oracle/proddb/9.2.0

. ./PROD_erp.env




http://appsdba.info

4

Prepare the source system (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 $ORACLE_HOME/appsutil/scripts/PROD_erp

.perl /adpreclone.pl dbTier




http://appsdba.info

5

(b) Prepare the source system application tier for cloning

Log on to the source system as the applmgr user and run the following commands.

$ cd $COMMON_TOP/admin/scripts/PROD_erp

$ perl adpreclone.pl appsTier




http://appsdba.info

6

Copy the Source Node File System

Log on to the source system application tier nodes as the APPLMGR user.

• Shut down the application tier server processes as shown below

cd $COMMON_TOP/admin/scripts/PROD_erp./adstpall.sh apps/appspassword




http://appsdba.info

7

• Copy the following application tier directories from the source node to the target

application tier node:

cd /d01/oracle

prodapplprodcomn

prodora

scp –pr proadappl applmgr@target_server:/d01/oracle

scp –pr proadcomn applmgr@target_server:/d01/oracle

scp –pr proadora applmgr@target_server:/d01/oracle

Once copied –

- Check the ownership as required

- Rename the directory

cd /d01/oracle

mv prodappl devappl

mv prodcomn devcomn

mv prodora devora




http://appsdba.info

8

Copy the database tier file system

Log on to the source system database Tier as the ORACLE user.• Perform a normal shutdown of the source system database

cd $RDBMS_ORACLE_HOME/appsutil/scripts/PROD_erp./addbctl.sh stop

• Copy the database (DBF) files from the source to the target system• Copy the source database ORACLE_HOME to the target system as shown below:

cd /d01/oraclescp –pr proaddb oracle@target_server:/d01/oracle

scp –pr proaddata oracle@target_server:/d01/oracleOnce copied – - Check the ownership as required- Rename the directory




http://appsdba.info

9

cd /d01/oraclemv proddb devdbmv proddata devdata

• Start up the source Applications system database and application tier processes

Configure the Target SystemOperating System of Target should be same as Source. Operating system should have allpre-requisite packages required for Oracle R11i before configuring 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).

Log on to target node as oracle user and run the following command and input your

values to each prompt as shown below :

$ cd /proddb/9.2.0/appsutil/clone/bin

$ perl adcfgclone.pl dbTier

Enter APPS Password :




http://appsdba.info

10




http://appsdba.info

11




http://appsdba.info

12

b. Configure the target system application tier server nodes

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

specify your values to each prompt as shown below.

$ cd /d01/oracle/devcomn/clone/bin

$ perl adcfgclone.pl appsTier

Enter the APPS password




http://appsdba.info

13




http://appsdba.info

14




http://appsdba.info

15




http://appsdba.info

16




http://appsdba.info

17




http://appsdba.info

18




http://appsdba.info

19

Above screenshots showing that all application services are started successfully. That

means, we have done cloning successfully.

Finishing Tasks

Post clone steps vary from client to client, here is the basic change.

Profile Option Name Changes at Site Level after Cloning

Site Name-> PROD, Change it to “DEV – Clone of PROD as of Dec 14 2010”

DEV – Clone of PROD as of 14-Dec-10

Login to Oracle Apps as SYSADMIN

Select System Administrator responsibility




http://appsdba.info

20

Profile –> System




http://appsdba.info

Now Oracle Apps Instance of DEV Looks Like:

cloning single to multi

Documents