Cloning Oracle Applications Release 12 with Rapid Clone

Section 1: Prerequisites

1. Run AutoConfig on the Application Tiers

Run AutoConfig on all application tier nodes. Use the adautocfg.sh command. All scripts
listed below are located in <INST_TOP>/admin/scripts.

Platform Functionality Command

UNIX Start Applications services adstrtal.sh
Stop Applications services adstpall.sh
Run AutoConfig adautocfg.sh

Attention: The database server and the database listener must remain available during the
AutoConfig run. Only the application tier servers should be shut down.
Note: Running AutoConfig may change your existing environment files. After running
AutoConfig, you should always set the environment before you run any Applications utilities,
in order to apply the changed environment variables.

2. Synchronize appsutil on the Database Tier Nodes

Update the RDBMS ORACLE_HOME file system with the AutoConfig files by performing
the following steps:

 On the application tier (as the APPLMGR user):

o Log in to the APPL_TOP environment (source the environment file)
o Create appsutil.zip file
perl <AD_TOP>/bin/admkappsutil.pl
o This will create appsutil.zip in <INST_TOP>/admin/out

 On the database tier (as the ORACLE user):

o Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>
o cd <RDBMS ORACLE_HOME>
o unzip -o appsutil.zip

3. Run AutoConfig on the Database Tier

Run AutoConfig on the database tier nodes. Use the adautocfg.sh/.cmd command. All the
scripts listed below are located in
<RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>.

Platform Functionality Command

UNIX Start database listener process addlnctl.sh start <SID>
Start database process addbctl.sh start
Stop database listener process addlnctl.sh stop <SID>
Stop database process addbctl.sh stop
Run AutoConfig adautocfg.sh

Attention: The database server and the database listener must remain available during the
AutoConfig run. All the other database tier services should be shut down.
Note: Running AutoConfig may change your existing environment files. After running
AutoConfig, you should always set the environment before you run any Applications utilities,
in order to apply the changed environment variables.

4. Maintain Snapshot information

Log in to each Applications Node as the APPLMGR user, and run "Maintain Snapshot
information" in AD Administration (adadmin).
Run adadmin  Select option 2  Select option 5  Select option 2  Select option 1

Section 2: Clone Oracle Applications Release 12

There are three phases to the cloning process:

1. Prepare the Source System
Execute the following commands to prepare the source system for cloning.
a. Prepare the source system database node 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 <INST_TOP>/admin/scripts
perl adpreclone.pl appsTier

2. Copy the Source System to the Target System

Scp –r <file to copy> oracle@<target system IP>:<Path where to copy)

Copy the application tier file system from the source Applications system to the target
 node by executing the following steps in the order listed. Ensure the application tier files
copied to the target system are owned by the target APPLMGR user, and that the database
node files are owned by the target ORACLE user.
a. Copy the application tier file system
Log on to the source system application tier nodes as the APPLMGR user.
 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>
 <COMMON_TOP>
 Tech Stack

Remove Existing direcotories

Rm –rdf <folder_name>

Note: Restore the backup of source Apps on target Apps.

 Tar –xzf <filename>.tar.gz <Target Location>

b. Copy the database node file system

Log on to the source system database node as the ORACLE user, and then:
 Perform a normal shutdown of the source system database
 Copy the database (DBF) files from the source to the target
system
 Copy the source database ORACLE_HOME to the target
system
 Start the source Applications system database and application tier
processes

Note: Restore the backup of source DB on target DB.

3. Configure 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 enter the following
commands to configure and start the database:
cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
perl adcfgclone.pl dbTier

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
Section 3: Finishing Tasks (If Required)

This section lists tasks that may be necessary, depending on your implementation and the
intended use of the cloned system.

1. Update profile options

Rapid Clone updates only site level profile options. If any other profile options are set to
instance specific values, you must update them manually.

2. Update printer settings

If the new cloned system needs to utilize different printers, update the target system with
the new printer settings now.
3. Update Workflow configuration settings
Cloning an Oracle Applications instance will not update the host and instance specific
information used by Oracle Workflow. Review the following tables and columns to verify
there is no instance specific data in the Workflow configuration on the target system.
Table Name Column Name Column Value Details
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE Value starts with
http://<old web host> :
Update to new web host
WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE Value starts with
"http://<old web host> :
Update to new web host
WF_SYSTEMS GUID Create a new system
defined as the new global
database name using the
Workflow Administrator
Web Applications
responsibility.
WF_SYSTEMS NAME Value needs to be
replaced with the
database global name
WF_AGENTS ADDRESS Update database link with
the new database global
name.
FND_FORM_FUNCTIONS WEB_HOST_NAME Update with the new web
host name
FND_FORM_FUNCTIONS WEB_AGENT_NAME Update to point at the
new PLSQL listener
name
FND_CONCURRENT_REQUESTS LOGFILE_NAME Update with the correct
path to the logfile
directory
FND_CONCURRENT_REQUESTS OUTFILE_NAME Update with the new
directory path on the
target system
4. Verify the APPLCSF variable setting
Source the APPS environment and review that the variable APPLCSF (identifying the
top-level directory for concurrent manager log and output files) points to a suitable
 directory. To modify it, change the value of the s_applcsf variable in the context file and
then run AutoConfig.
5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the target system is in a different domain name than the source system and
SESSION_COOKIE_DOMAIN was not null in the source system, update that value to
reflect the new domain name.

Reference: Metalink Note 406982.1 and 387859.1