You are on page 1of 26

Advanced Cloning Options

Copyright 2007, Oracle. All rights reserved.


Objectives

At the end of this module, you should be able to do the


following:
Refresh a cloned target system
Clone a single-node system to a multi-node system
Clone a multi-node system to a multi-node system
Add a node to an existing system
Reduce the number of nodes in a multi-node system

1-2 Copyright 2007, Oracle. All rights reserved.


Module Overview

This module consists of the following topics:


Refresh a cloned target system
Clone a single-node system to a multi-node system
Clone a multi-node system to a multi-node system
Add a node to an existing system
Reduce the number of nodes in a multi-node system

1-3 Copyright 2007, Oracle. All rights reserved.


Advanced Cloning Options

Advanced cloning options include:


Refreshing a target system
Cloning multi-node systems
Adding a new node to an existing system

1-4 Copyright 2007, Oracle. All rights reserved.


Refreshing a Target System

You may need to refresh a target system periodically, to


synchronize it with changes made on the source system
Prepare the source system (as described previously)

1-5 Copyright 2007, Oracle. All rights reserved.


Refreshing a Target System

Copy any parts of the application tier file system that have
been updated on the source system
The APPL_TOP, COMMON_TOP, or technology stack may
need to be refreshed on the target system
Copy the database node file system if the
RDBMS_ORACLE_HOME or database
need to be refreshed
If refreshing the database, refresh the
RDBMS_ORACLE_HOME at the same time

1-6 Copyright 2007, Oracle. All rights reserved.


Refreshing a Target System

Configure the target system to be refreshed by specifying


the existing target system when running adcfgclone
commands:

perl adcfgclone.pl dbTier \


<Database tier context file on target>

perl adcfgclone.pl appsTier \


<INST_TOP/appl/admin/<Application tier context
file on target>

1-7 Copyright 2007, Oracle. All rights reserved.


Refreshing a Target System

Where applicable, carry out the finishing tasks described


earlier

Target

Source

1-8 Copyright 2007, Oracle. All rights reserved.


Cloning Multi-Node Systems

You can use Rapid Clone in cases where the source or target
system has a multi-node application tier
With Release 12, only one copy of the files for the
application tier nodes needs to be copied to the target
system, regardless of shared file system usage

Target Multi-Node Application Tier


(Shared File System)

Source

1-9 Copyright 2007, Oracle. All rights reserved.


Cloning Multi-Node Systems

Details of adding shared file system application tier nodes


are described in OracleMetaLink Note 384241.1
If adding non-shared nodes, the copy and configure steps
must be performed as on the primary node

Target
Multi-Node Application Tier
(Non-Shared File System)

Source

1 - 10 Copyright 2007, Oracle. All rights reserved.


Adding a New Node to an Existing System

You can also use Rapid Clone to set up a new node


being added to an existing Applications system
The new node can either run the same services as the
source node, or different services
Prepare the source system, copy it to the new node and
configure it as applicable
After adcfgclone completes, set up the environment and
run the following commands on the target system:

cd <COMMON_TOP>/clone/bin
perl adaddnode.pl

1 - 11 Copyright 2007, Oracle. All rights reserved.


Refresh a Cloned Target System

Prepare the source system


Copy the source system to the target system
Configure the target system
Perform finishing tasks

Target

Source

1 - 12 Copyright 2007, Oracle. All rights reserved.


Prepare the Source System

Prepare the source system database tier for cloning


Prepare the source system application tier for cloning

Target

Source

1 - 13 Copyright 2007, Oracle. All rights reserved.


Copy the Source System to the Target System

Copy the application tier file system if the APPL_TOP,


OracleAS 10.1.2 ORACLE_HOME, or OracleAS 10.1.3
ORACLE_HOME need to be refreshed
Copy the updated portion of the application tier file system
Copy the database tier file system if the RDBMS
ORACLE_HOME or the database needs to be refreshed
If refreshing the database, the ORACLE_HOME should be
refreshed at the same time

Target
Source

1 - 14 Copyright 2007, Oracle. All rights reserved.


Configure the Target System

Specify the existing target system context file when running


adcfgclone.pl commands:
perl adcfgclone.pl dbTier <Database target
context file>

where database context file is:


<RDBMS ORACLE_HOME>/appsutil/
<Target CONTEXT_NAME>.xml

perl adcfgclone.pl appsTier <Application tier


target context file>
where application tier target context file is:
<INST_TOP>/appl/admin/<Target CONTEXT_NAME>.xml

1 - 15 Copyright 2007, Oracle. All rights reserved.


Finishing Tasks

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 utilizes different printers, update the
target system with the new printer settings
3. Update Workflow and other configuration settings
Cloning an instance will not update the host- and instance-
specific information used by Oracle Workflow and other
components
Refer to the following slides to confirm there is no instance-
specific data on the target system

1 - 16 Copyright 2007, Oracle. All rights reserved.


Clone a Single-Node System to
a Multi-Node System
This procedure allows the original single node system to be
cloned into a multi-node system

1 - 17 Copyright 2007, Oracle. All rights reserved.


Clone a Single Node System to
a Multi-Node System

Perform the following sections from the Cloning Oracle


Applications module to clone a single-node system to multi-
node system:
Perform prerequisites
Clone Oracle Applications
Finishing Tasks

1 - 18 Copyright 2007, Oracle. All rights reserved.


Prerequisite Steps

Perform the following prerequisite steps on the source and all


target nodes:
1. Verify source and target nodes software versions
2. Apply the latest Rapid Clone patch (if applicable)
3. Set up Rapid Clone on the application tier
4. Set up Rapid Clone on the database tier

1 - 19 Copyright 2007, Oracle. All rights reserved.


Clone Oracle Applications

There are three phases to the cloning process:


Prepare the source system
Copy the source system to the target system
Configure the target system

Target
Configure

Copy

Source
Prepare

1 - 20 Copyright 2007, Oracle. All rights reserved.


Finishing Tasks

Update profile options


Update printer settings
Update Workflow and other configuration settings

Target
System

Source
System

1 - 21 Copyright 2007, Oracle. All rights reserved.


Cloning a Multi-Node System to
a Multi-Node System

A multi-node system can be cloned if the number of nodes


and distribution of servers in the target system matches that
of the source system
To clone a multi-node system to a multi-node system,
perform the cloning process on each node
For example, if the source system contains three nodes,
perform the cloning process three times:
Clone source system node 1 to target system node 1
Clone source system node 2 to target system node 2
Clone source system node 3 to target system node 3

1 - 22 Copyright 2007, Oracle. All rights reserved.


Adding a Node

Use Rapid Clone to clone a node and add it to the existing


Application System
Follow the instructions in the Application Tier part of Cloning
Oracle Applications Release 12 (OracleMetaLink Note
406982.1):
Prepare the source system, copy it to the new node and
configure it
After adcfgclone.pl completes, source the Applications
environment and run the following commands on the target
system:
cd <COMMON_TOP>/clone/bin
perl adaddnode.pl

1 - 23 Copyright 2007, Oracle. All rights reserved.


Reducing the Number of Nodes

Reduce the number of nodes of a multi-node system by


merging the APPL_TOPs
Use Rapid Clone to clone a multi-node system to a single-
node system (or a multi-node system with fewer nodes) by
merging the APPL_TOP file systems

1 - 24 Copyright 2007, Oracle. All rights reserved.


Module Summary

In this module, you should have learned how to do the


following:
Refresh a cloned target system
Clone a single-node system to a multi-node system
Clone a multi-node system to a multi-node system
Add a node to an existing system
Reduce the number of nodes in a multi-node system

1 - 25 Copyright 2007, Oracle. All rights reserved.


Module Discussion

Name some situations that may require refreshing a cloned


Oracle Applications system
When cloning a single-node system to a multi-node, what
are the limitations on the number of nodes?

1 - 26 Copyright 2007, Oracle. All rights reserved.

You might also like