+ All Categories
Home > Documents > Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ......

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

Date post: 22-Feb-2018
Category:
Upload: vuongkhanh
View: 276 times
Download: 1 times
Share this document with a friend
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 which is AutoConfig enabled using Rapid Clone from one to three nodes, it includes Port Selection, Forms Server, Reports Server, Apache Server and Concurrent Processing, also all the scripts or programs which are used to startup up and shutdown all the services. The cloning word means to do a functional copy of an existing environment. Simply copying the application directories doesn’t mean that our new environment will work properly, we need to do some additional steps or tasks to have a functional environment. CLONE Single Server to Two Node Server SOURCE Server PROD DB Tier prodb proddata Apps Tier prodcomn prodappl prodora TARGET Server DEV DB Tier devdb devdata TARGET Server DEV Apps Tier devcomn devappl devora
Transcript
Page 1: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

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 which is AutoConfig enabled using Rapid Clone from one to three nodes, it includes Port Selection, Forms Server, Reports Server, Apache Server and Concurrent Processing, also all the scripts or programs which are used to startup up and shutdown all the services. The cloning word means to do a functional copy of an existing environment. Simply copying the application directories doesn’t mean that our new environment will work properly, we need to do some additional steps or tasks to have a functional environment. CLONE – Single Server to Two Node Server

SOURCE Server – PROD

DB Tier

prodb

proddata

Apps Tier

prodcomn

prodappl

prodora

TARGET Server – DEV

DB Tier

devdb

devdata

TARGET Server – DEV

Apps Tier

devcomn

devappl

devora

Page 2: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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 or to

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 node for database server and second node is for Application. That means all application services will reside on one node and database on a separate node. Our source node is ERP and target node is also ERP. And our source database node is PROD and Target database node is DEV. The TARGET directory 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 system must have same component versions & operating system type. And also we cannot clone from windows to linux.

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

su applmgr

cd /d01/oracle/prodappl

. ./APPSORA.env

Page 3: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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

Page 4: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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

Page 5: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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

Page 6: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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

Page 7: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

7

• Copy the following application tier directories from the source node to the target application tier node: cd /d01/oracle prodappl prodcomn 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

Page 8: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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/oracle scp –pr proaddb oracle@target_server:/d01/oracle scp –pr proaddata oracle@target_server:/d01/oracle Once copied – - Check the ownership as required - Rename the directory

Page 9: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

9

cd /d01/oracle mv proddb devdb mv proddata devdata

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

Configure the Target System Operating System of Target should be same as Source. Operating system should have all pre-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 :

Page 10: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

10

Page 11: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

11

Page 12: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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

Page 13: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

13

Page 14: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

14

Page 15: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

15

Page 16: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

16

Page 17: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

17

Page 18: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

18

Page 19: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

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

Page 20: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

20

Profile –> System

Page 21: Cloning a Single-Node System To a Multi-Node System a Single-Node System To a Multi-Node System ... also all the scripts or ... • To create a test environment from an existing production

Author – A.Kishore/Sachin

http://appsdba.info

21

Now Oracle Apps Instance of DEV Looks Like:


Recommended