Multi-node to Single node 4 Footnotes on List Recloning of the database only can be useful if the source system has changed, and the target system needs to be updated with these changes. A cloned system created with Rapid Clone can be used as the source system for another round of cloning. See Chapter 9 for details. For further details of cloning options and strategies, see My Oracle Support Knowledge Document
If the target database is a RAC database, the Target Database Details region is rendered differently, as shown in the following figure.
Specify whether SCAN is configured in the target database. Enter RAC Target database details, if applicable.
This step only applies if R12 cloning target database is a RAC database. This step is skipped if the target database has the type Single Instance. If the source Oracle E-Business Suite technology stack has the required patches applied for configuring customized names for listeners, then this page will automatically render in such a way that you provide names for the target database listeners by providing the required names in the column "New Listener Name".
R12 cloning is highly recommended not to change these values if it automatically populated. If for some reason the SCAN Name and SCAN Port fields are not populated for example, if the cluster target instance discovered in Enterprise Manager has not populated these values yet as propertiesthen you must enter the correct values for these fields.
Apr 01, · This post gives example of Cloning of EBS R running on OEL 6 64 bit using Rapid Clone. Oracle EBS R Cloning with Step by Step DB Tier Cloning 1. Prepare source node for Cloning Prepare source node for Database Cloning. High level Steps Involved to do the R upgrade steps are: timberdesignmag.comd Pre requestions for R timberdesignmag.com ETCC in both database tier and. Apr 02, · c) Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release (Doc ID ).
If the source Oracle E-Business Suite technology stack does not have the required patches, then the "Custom SCAN Details" section will not be rendered, and the target database will be configured with virtual host names. Enter source and target information.
In this step, Smart Clone captures information related to the source and target. All application tier information of the source Oracle E-Business Suite system is displayed.
You enter details for the target Oracle E-Business Suite system. If the source Oracle E-Business Suite system is deployed on a single applications tier, the Source regions appear as shown in the following figure.
Information is shown for the following services: In the Available Target System Nodes region, choose the source host that can be used as a reference while cloning the target applications tier. If the source Oracle E-Business Suite system is deployed on a multi-node applications tier, then the Source regions appear as shown below.
The Source System Nodes region shows the details of the source Oracle E-Business Suite applications tier in terms of Number of nodes the applications tier is deployed on.
Details of the services on the nodes. For a Release 11i multi-node applications tier system, you will need to choose the nodes for the services which are to be used as references for creating the Release 11i single node applications tiers.
For Release 12, selecting the service in this section is unnecessary because the reference source host will be selected only from the "Available Target System Nodes" region.
This is the default option. Then choose the source host that can be used as a reference while cloning the target applications tier.
For the target system node, click the Specify Details icon to update its properties in the Target Node Summary page. The Target Node Summary page is shown below. The port pool and individual port values are updated from the source instance.
If there is an invalid value in the port pool from the source instance, the following error is shown: Setting to default value '0'.
Please update as needed! In the Copy Parameters step, enter information on how the copying process should be done. If you are using the same host for both the source and target instance, ensure that the source stage directory is different from the target stage directory.
Smart Clone uses named credentials. You can select and test the named credentials on this page. Smart Clone requires the following credentials to be created: Database schema credentials appear only when the source applications system is on Release 11i and using a non-shared file system.
The Credentials page for a Smart Clone procedure where the source applications system is multi-node and the target database is non-RAC is shown in the figure below. This page allows you to enter in and test all required credentials for the nodes. The Credentials page for a Smart Clone procedure where the source applications system is single node and the target database is RAC is shown in the figure below.
On this page you can enter and test the required credentials for all the nodes. Enter values for custom parameters. These would be used in any directive steps you have created.
You can create directive steps to be integrated into a deployment procedure. For a description on how to create a directive step and insert it into a procedure created using the "Create Like" feature and a shipped Smart Clone procedure, see:Oracle Apps DBA R12 Interview Questions.
What do we have in FND_NODES? Answer: FND_NODES table contains information about node_names and services enabled on a node. In multinode instance if you want to know which node is running what services, You can query the fnd_nodes and get that information.
Hello all, After long time I am updating my blog with R cloning. There is a slight difference between R and R With the introduction of dualfs in R we can even configure patch filesystem with single run of adcfgclone on the target node.
In this article, i am going to present the cloning procedure on E-business suite R environment. The main procedure to clone an e-business suite environment in R is same except to clone the patch file system in target clone environment.
E-Business Suite Cloning Procedure1. EBS R12 CLONING Author: Godfrey I Maema Applications DBA Certified Professional Oracle. Oracle EBS R Cloning with Step by Step DB Tier Cloning 1. Prepare source node for Cloning Prepare source node for Database Cloning.
High level Steps Involved to do the R upgrade steps are: timberdesignmag.comd Pre requestions for R timberdesignmag.com ETCC in both database tier and. This is the second in a series of articles about common technical myths or misunderstandings about the E-Business Suite.
Other articles have covered installations, patching, migrations, upgrades, and maintenance. This article discusses cloning. Subsequent articles will cover patching, migrating.