Our company runs Oracle E Business Suite 11.5.9 and 11.5.10, mostly application and database server running 24×7 to support production. We have own development team to enhance our applications regarding the user needs. And sometime our development team needs to refresh development server with current data and applications from production server. But we don’t have enough time to cloning applications and database if we have to shut it down first. To solve this problem, we have a solution to “On-line” cloning application and database from production into development. Some of these steps can be found on Note: 230672.1. 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.
a. For Application, we can copy it although the applications still using by user. We don’t need to 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
· <COMMON_TOP>/clone
· <COMMON_TOP>/_pages (when this directory exists)
· <806 ORACLE_HOME>
· <iAS ORACLE_HOME>
b. For Database, we will do these steps :
· Copy the database (DBF) files from the source to the target system using Hot Backup, we don’t need to shut the database down :
§ SQL> Alter Database Backup Controlfile to Trace;
(The trace file can be found on user_dump_dest directory, this file used for create control file on the target system).
§ SQL> select sequence# from v$log where status = ‘CURRENT’; (to get the first archive log before hot backup)
§ Alter tablespace Begin Backup
§ Copy the datafiles from source system to the target system
§ Alter tablespace End Backup
§ SQL> select sequence# from v$log where status = ‘CURRENT’; (to get the latest archive log after hot backup)
§ SQL> alter system switch logfile;
§ After that, copy the first and the latest archive log files (that we got from step 1 and 5) from the source system into the target system.
· Copy the source database ORACLE_HOME to the target system
3. Configure the Target System
Execute the following commands to configure the target system.
a. Configure the target system database server
To configure the database, first we can do as we do clone a database (Note: 224274.1). After the database open, log on to the target system as the ORACLE user and type the following commands to configure:
# cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
# perl adcfgclone.pl dbTechStack
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.
And now, our development team no needs waiting for so long to get the scheduled downtime of the production environment, if they need to refresh the development server they can ask DBA anytime.
