Cloning Oracle Applications Release 11i with Rapid Clone

(Multi-node to Multi-node)
(Base Note: 230672.1, FAQ Note: 216664.1)
All the pre-requisites including required patches have been taken care of on the source
systems itself so we dont need to do that again.
Multi-node to Multi-node Cloning
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.
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. Start the EMC disk cloning process
Start the disk clone using EMC clone to bring it to a consistent state. Talk to the
EMC administrator to start this process.
b. Prepare the source system database tier for cloning
Log on to the source system as the ORACLE user, source the environment and
run the following commands:
cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
perl adpreclone.pl dbTier
c. Prepare the source system application tier for cloning
Log on to the source system as the APPLMGR user, source the environment 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
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 tier files are owned by the 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

Zip the file system in /u01/app directory using the tar command:
cd /u01/app
tar czvf erpappl-dev.tgz erpapp*
tar czvf erpcomn-dev.tgz erpcom*
tar czvf erpora-dev.tgz erpor*
OR

Copy the tar files to the target server node in the /u01/app directory.
The following are the directories suggested by Oracle to be copied but we
will copy the entire apps file system, as mentioned above:
<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. Copy the database tier file system
Log on to the source system database node as the ORACLE user.

Perform a normal shutdown of the source system database

Once the EMC disks are consistent, contact the EMC administrator to
fracture the EMC clone to separate the disks

Copy the source database ORACLE_HOME to the target system using

the tar utility
cd /u01/app
tar czvf oracle-dev.tgz oracl*

Copy the /etc/oraInst.loc file from the source system into the same
location on this host.

Start up the source Applications system database and application tier

processes

Note: Unix/Linux users, make sure that the softlinks are preserved when copying.

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 ASM for the Target System server

Login as root on the target system and reinstate the crs services for this
new target system.
cd $ORACLE_HOME/bin
./localconfig add reset

Login to the target system as the ORACLE user, source the environment
file that has been copied from the source system and export the
ORACLE_SID to the ASM instance.

Next, Login to SQL*Plus and startup the ASM instance since the init and
spfile for the ASM systems have been copied over from the source
system.

b. 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

Ensure that the oraInventory registration is successful.

If you get an error message to run registration manually using some
script, Login back as the root user and run the script. After that change
owner of the entire /etc/oraInventory directory to oracle:dba. That may
work too.
chown -R oracle:dba /etc/oraInventory
chmod -R a+rw /etc/oraInventory

c. Add the entry for ASM listener to the ifile pointed by tnsnames.ora
Add the ASM listener to the <context_name>_ifile.ora file.
e.g.
LISTENER_+ASM =
(ADDRESS = (PROTOCOL = TCP)(Host = ocrp.circoncorp.com)(Port = 1524))
d. Recreate the env file link
Remove the link file to the env directory (DEV10.env). Add a soft link for the new
environment file.
cd /u01/app/oracle
rm DEV10.env
ln 10.2EE/CRP_ocrp.env CRP10.env
e. 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

Multi-node to Single Node

Run the Pre-clone process for merge

Follow the same pre-clone process for DB Tier as for Multi-node to Multi-node.

Login to the DB Node (DB, Admin, Concurrent Manager) as the applmgr user and run
the appsTier merge from the erpcomn/admin/scripts/<context_name> directory. This will
be the primary node where all the services will be moved.
cd /erpcomn/admin/scripts/<context_name>
perl adpreclone.sh appsTier merge

Login to the Forms/Web Node (Forms, Web) as the applmgr user and run the appltop
merge from the erpcomn/admin/scripts/<context_name> directory. This is the secondary
node.
cd /erpcomn/admin/scripts/<context_name>
perl adpreclone.sh appltop merge

Copy the required files for merging

Follow the same process for DB Tier as for Multi-node to Multi-node.

For the Apps Tier, login as the APPLMGR user to each source node (Forms/Web) and
recursively copy:
directory <COMMON_TOP>/clone/appl
- to
directory <COMMMON_TOP>/clone/appl on Node A
(or the copy of Node A).

Configure the application tier server nodes

Follow the same process for DB Tier as for Multi-node to Multi-node.
For Apps Tier:
o Shut down all services on each application tier node, including Node A. The
database and its listener should remain up.
o Log in to the merged APPL_TOP node as the APPLMGR user and execute the
following commands:
o $ cd <COMMON_TOP>/clone/bin
$ perl adcfgclone.pl appsTier

Final tasks
o Log in to the target system application tier node as the APPLMGR user.
o Run the following tasks in adadmin for all products:
generate JAR files
generate message files
relink executables
copy files to destination
o Rename the custom..env files for application tier to use the new instance naming
convention

Copy the remaining files from the Forms/Web node(s)

Depending on which tier you chose as the primary node, certain files may be missing.
Run adadmin to verify files required at runtime. If any files are listed as missing files, you
must manually copy them to the merged APPL_TOP.
Remove the temporary directory <COMMON_TOP>/clone/appl to reduce disk space
usage.

Finishing Tasks (Applies to all Clone Tasks)

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

WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE

WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE

WF_SYSTEMS

GUID

WF_SYSTEMS

NAME

WF_AGENTS

ADDRESS

Column Value Details

Value starts with http://<old
web host> : Update to new
web host
Value starts with "http://<old
web host> : Update to new
web host
Create a new system defined
as the new global database
name using the Workflow
Administrator Web
Applications responsibility.
(No need to do this cloning
process automatically takes
care of this)
Value needs to be replaced
with the database global
name (No need to do this
cloning process automatically
takes care of this)
Update database link with the
new database global name.
(No need to do this cloning
process automatically takes
care of this)

Update with the new web

WEB_HOST_NAME host name (No changes
required here)
Update to point at the new
FND_FORM_FUNCTIONS
WEB_AGENT_NAME PLSQL listener name (No
changes required here)
Update with the correct path
FND_CONCURRENT_REQUESTS LOGFILE_NAME
to the logfile directory (No
changes required here)
Update with the new directory
FND_CONCURRENT_REQUESTS OUTFILE_NAME
path on the target system (No
changes required here)
FND_FORM_FUNCTIONS

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 an
acceptable directory. To modify it, change the value of s_applcsf in the contextfile
and 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.
6. Rename the custom..env files for application tier to use the new instance
naming convention
7. Archive Logs on Database
Check the archive log settings on the database. Take appropriate action as to
disable or enable archive logs on the target system.
Startup mount
Alter database noarchivelog;
8. Configure Workflow mailer
Set the Workflow notification mailer to manual and keep it down for non-PRD
systems. Also change the Mail account that the system uses appropriately to the
new system.
For TST, the mail account is ora_tst_wkflo, for DEV its ora_dev_wkflo and for PRD
its ora_wkflo.
For all other systems we will use the ora_tst_wkflo account.
9. Backup Apps file system and database
Backup the file system on all tiers and the database also. Shutdown the system
including the DB and ASM. Tar all the folders on all nodes and put the under
/backup/<instance_name>/fs/.. folders.
10. Create a DBID file in the /backup/<instance_name> folder.

11. Create a backup control file and keep it in /backup/<instance_name> folder.

12. Create Register Database ID for Vertex.
13. Set the Site_Name and Java Color Scheme profile options
14. Reset (Cancel) the concurrent jobs. All jobs not run by SYSADMIN.