Clone appsdba

                                                     
 1  
Contents  
1> What is Cloning and How to do Single Node        Cloning on Single machine       Page 2 - 2
2> Cloning prerequisites steps      Page 3 - 4
3> Prepare Source System       Page 5 - 6
4> Copy Source Node File System     Page 7 - 8
5> Configure Target System      Page 8 – 10
6> Finishing Tasks        Page 10 - 11      

                                                             
 2
What is Cloning and How to do Single Node cloning on Single machine
Cloning is the act of creating an identical copy of an already existing Production Oracle Applications system.
Simply copying all of the components from source to target system does not provide us a working Oracle Applications system, there are various configuration files that must be changed & for this purpose we do Cloning.
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.
We will 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.  
Note: 135792.1 - Cloning Oracle Applications Release 11i Note: 406982.1- Cloning Oracle Applications Release 12 with Rapid Clone
In this Cloning demonstation, we will clone our Oracle R12 PROD single node instance to DEV instance. Even we are doing single node cloning, we will have to take dbTier and appsTier as two nodes. Our source and target node is ERP. And our source database node is PROD and Target database node is DEV. The TARGET directory structure is same .
                                                                                                                                                                                       
 3
 Cloning 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 can not clone from windows to linux.
We need to perform certain prerequisites steps before cloning the source system:
 Login as Applications file user & run the environment file.
su applmgr
cd /d01/oracle/PROD/apps/apps_st/appl
. ./APPSPROD_erp.env  
                                                                                                                                                                                 
 4
Login to database tier and set the environment.  
su oracle cd /d01/oracle/PROD/db/tech_st/10.2.0 . ./PROD_erp.env  
                                                           
 5
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
(b) Prepare the source system application tier for cloning
Log on to the source system as the APPLPROD user and run the following commands.
$ cd $/$ADMIN_SCRPTS_HOME
$ perl adpreclone.pl appsTier
                                                                                                                                Author –                                                            
 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 $ADMIN_SCRIPTS_HOME
./adstpall.sh apps/appspassword
• Copy the following application tier directories from the source node to the target application tier node:
                cd /d01/oracle/PROD
                 apps   - Copy only apps directory
Note - No need to copy inst – perl adcfgclone.pl will create inst
scp –pr d01/oracle/PROD/apps applmgr@target_server:/d01/oracle/DEV
Once copied –
- Check the ownership as required
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 following application tier directories from the source node to the target application tier node:
                                                                                                                                Author –                                                            
 7
scp –pr d01/oracle/PROD/db/tech_st/10.2.0 oracle@target_server:/d01/oracle/DEV/db/tech_st/10.2.0
scp –pr /d01/oracle/PROD/db/apps_st/data oracle@target_server:/d01/oracle/DEV/db/apps_st/data
Once copied –
- Check the ownership as required
• 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 prerequisite packages required for Oracle R12 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)  
(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  
                                                                                                                                Author –                                                            
 8  
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  
………………………………………………………………………………………………………….
                                                                                                                                Author –                                                            
 9
………………………………………………………………………………………………………….
All enabled services for this node are started. Existing with status 0    
                                                                                                                                Author –                                                          
 10
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 15-Dec-10”
Connect to System Administrator
Profile – System  
                                                         
 11    
Now Oracle Apps Instance of DEV Looks Like: