Rapid Clone

Cloning Tasks

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.

Note: Rapid Clone never changes the source system configuration.

The cloning process consists of three phases, each of which is made up of several logical sections and their steps.

1. Prepare the source system
   1. Execute the following commands to prepare the source system for cloning:
      1. Prepare the source system database tier for cloning
         1. Log on to the source system as the ORACLE user, and run the following commands:

1. Note: If new Rapid Clone or AutoConfig updates are applied to the system, adpreclone.pl must be executed again on the dbTier and on the appsTier in order to apply the new files into the clone directory structures that will be used during the cloning configuration stage.

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 node files are owned by the target ORACLE user.

Note: In the copying tasks below, UNIX/Linux users should ensure that the symbolic links (soft links) are preserved when copying. On most UNIX platforms, this can be accomplished with the cp -RH command. Consult the UNIX man page for the cp command to check the parameters available on your platform.

For example: cd /target_dest_dir/db cp -RH /source_dir/db/*

Alternatively, the tar command can be used to compress the directories into a temporary staging area. If you use this command, you may require the -h option to follow symbolic links, as following symbolic links is not the default behavior on all platforms. Consult the UNIX man page for the tar command.

Additionally, verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root (i.e. nmo, nmhs, nmb, etc).

1. Copy the application tier file system
   1. Log on to the source system application tier nodes as the APPLMGR user and 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]
      • Applications Technology Stack:
        • [OracleAS Tools ORACLE_HOME]
        • [OracleAS Web IAS_ORACLE_HOME]

Copy the database node file system

Log on to the source system database node as the ORACLE user, and then:

1. Perform a normal shutdown of the source system database
2. Copy the database (.dbf) files from the source system to the target system
3. Copy the source database ORACLE_HOME to the target system
4. Start the source Applications system database and application tier processes

Comparison

—In 11i you copy $APPL_TOP, $OA_HTML, $OA_JAVA, $OA_JRE_TOP, $COMMON_TOP/util, $COMMON_TOP/clone, 806 & iAS

ORACLE_HOME,

Database ORACLE_HOME & DB_TOP

—In R12/12i you copy $APPL_TOP, $COMMON_TOP, Forms & Reports ORACLE_HOME (10.1.2), Web IAS_ORACLE_HOME (10.1.3) ,

Database

ORACLE_HOME & DB_TOP

Configure the target system

Run the following commands to configure the target system. You will be prompted for specific target system values such as SID, paths, and ports.

1. Configure the target system database server
   1. Log on to the target system as the ORACLE user and enter the following commands:

Section 3: Finishing 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
   1. 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
   1. 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
   1. Cloning an Oracle Applications instance will not update the host and instance-specific information used by Oracle Workflow. Review the tables and columns listed in Table 3 to check for any instance-specific data in the Workflow configuration on the target system.
      1. Table 3: Workflow configuration settings

1. Verify the APPLCSF variable setting
   1. 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.
2. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
   1. 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.
3. Re-Implement SSL and SSO configuration
   1. If the Source System was SSL or SSO enabled, reconfigure the Target by following the SSL/SSO documentation.

=====================================================================================================

FROM onlineoracleappsdba.com

=====================================================================================================

RAPID CLONE

Basically for cloning Oracle Application it can be categorised into three major categories.

-Preparing the Source System

-Copy the file System

-Preparing or say Configuring the Target System

You can achive first and third steps using a Rapid Clone utility which Oracle provides for cloning

There can be many ways and methods to clone Oracle Application which many organisations follows but the only supported method provided by Oracle is using Rapid clone.

Rapid Clone is the new cloning utility introduced in Release 11.5.8. Rapid Clone leverages the new installation and configuration technology utilized by Rapid Install.

Basically there are two cloning methodology using Autoconfig and without using autoconfig. First one that is using autoconfig is completely replaced by Rapidclone.

Non-autocofig cloning methodology was generally used before 11.5.5 that is non autoconfig enabled system.

Here I will discuss Rapid Clone method of cloning and also throw some light on cloning 11.0.3 oracle application as some users are still using that.

So first about the Rapid clone method.

In Category 1 that is first you need to make source for clone. You need to dress up Source system so that only configuration files and not the whole file system is copied.

Pre-requiste Steps

To start with cloning you need to first check about some pre-requisites some utilities should be of required version

Here are they,

Oracle Universal Installer should be of 2.2.0.19 version

Perl should be of 5.005 version minimum

JRE 1.1.8 and 1.3.1

JDK 1.3.1

Zip utility of version 2.3 minimum

Latest Autoconfig Templates patches are applied. TXK-O is the latest till date.

Latest Rapid Clone patches should be applied. Latest is ADX.F till date.

After check ing the pre-requisites now your system is ready to clone.

Preparing the Source system:

After checking the above mentioned pre-requisites now you have to prepare the source system which need to be cloned.

In a broad way what this step will do is this will create the staged clone directory which will be having the driver files and configuration file of the source.

So what exactly is going to happen in this step. Lets get in more details

Basically you have to run the adpreclone.pl script once for Application tier and one for the datbase (even if you are on single node ! )

Lets first check for the Database tier

On Source system, run following as ORACLE user

cd RDBMS Oracle_Home/appsutil/scripts/_perl ./adpreclone.pl dbTier

After running this it goes in two stages

dbTechstack and Database

What exactly it will do is

It will create stage cloned area at $ORACLE_HOME/appsutil/clone This clone directory has got following main directories

data,jre,bin,db,html,context

It will prepare datbase techstack at dbTechStack stage. Major activities it will take care of at this stage.

-Creates template files at $ORACLE_HOME/appsutil/template

-Creates driver files at $ORACLE_HOME/appsutil/driver/instconf.drv

-Converts inventory from binary to xml

It will prepare datbase at the database stage. Major activities includes

-Create datbase control file script

$Oracle_Home/appsutil/clone/context/data/stage/addbhomsrc.xml

$Oracle_Home/appsutil/clone/context/data/stage/adcrdb.zip

adcrdbclone.sql

-Generates database creation driver file

$Oracle_Home/appsutil/clone/context/data/driver/data.drv

-Copy JDBC Libraries

$Oracle_Home/appsutil/clone /clone/jlib/classes111.zip

So all this happens on database side

Now lets concentrate on Application tier side. Again it goes almost in the same way that is in two stages.

As a APPLMGR user on application tier this script is run

cd $COMMON_TOP/admin/scripts/_perl ./adpreclone.pl appsTier

It will also create the staged clone directory at $COMMON_TOP/clone

It goes in two stages. Lets see one by one

atTechStack that is Application tier techstack.

- Creates template files for

Oracle_iAS_Home/appsutil/template

Oracle_806_Home/appsutil/template

-Creates Techstack driver files for

Oracle_iAS_Home/appsutil/driver/instconf.drv

Oracle_806_Home/appsutil/driver/instconf.drv

appltop preparation

-It will create application top driver file

$COMMON_TOP/clone/appl/driver/appl.drv

-Copy JDBC libraries

$COMMON_TOP/clone/jlib/classes111.zip

So this all happens in dressing the source system

After then we need to copy the files.

Copy following files

APPL_TOP

OA_HTML ($COMMON_TOP/html)

JAVA_TOP

COMMON_TOP/util

COMMON_TOP/clone

8.0.6 ORACLE_HOME

iAS ORACLE_HOME

DB ORACLE_HOME

dbf files

After this stage now you need to configure the Target node. Basically you will run adcfgclone.pl same for databse tier and for application tier.

Let go in bit more detail:

First we will see for the database tier

On the target node you will run

ORACLE_DB_HOME/appsutil/clone/bin/perl adcfgclone.pl dbTier

Again there are two stages :

First will look at dbTechstack

It will use the driver files and templates which were created at source and has been copied to target.

Following scripts are run

-adchkutl.sh

-adclonectx.pl

-runInstallConfigDriver —- located in $Oracle_Home/appsutil/driver/instconf.drv

-Relinking $Oracle_Home/appsutil/install/adlnkoh.sh

Now for database

-Driver file

$Oracle_Home/appsutil/clone/context/data/driver/data.drv

-Create database adcrdb.zip

-Autoconfig is run

-Control file creation adcrdbclone.sql

Now on application tier

from COMMON_TOP/clone/bin/perl adcfgclone.pl appsTier

Stage at TechStack

-Creates context file for target adclonectx.pl

-Run driver files

$Oracle_806_Home/appsutil/driver/instconf.drv

$Oracle_iAS_Home/appsutil/driver/instconf.drv

Relinking of Oracle Home

$Oracle_806_Home/bin/adlnk806.sh

$Oracle_iAS_Home/bin/adlnkiAS.sh

at the end for ApplTop stage

It runs driver and then autoconfig

So this will totally configure your application which has been copied.

At the end you have to some finishing tasks

-Update Printer settings

-Update Workflow Configuration settings

-Update Profile options

This completes you application cloning completely.