Beruflich Dokumente
Kultur Dokumente
info
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.
Login as Applications file user & set the environment file on source node. su applmgr cd /d01/oracle/prodappl . ./APPSORA.env
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
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
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
cd /d01/oracle mv proddb devdb mv proddata devdata Start up the source Applications system database and application tier processes
10
11
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.
12
13
14
15
16
17
18
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
19
20
21