Questions Metalink Doc ID: Note:216664.1 Cloning Concepts What is cloning? How can I clone an Oracle Applications system? What are the differences between the two cloning methods? What is the AD Cloning utility? What is Rapid Clone? How do I determine whether my system is Rapid Clone enabled? What is AutoConfig? How do I determine whether my system is AutoConfig enabled? We are running Release 11.5.7 (or any prior release), which cloning method can we use? We are running Release 11.5.8 (or any later release), which cloning method can we use? Our Oracle Applications system is on Windows, which cloning method can we use? We have a Platinum installation of Oracle Applications. Can we clone our system? Can I clone from one operating system version to another? Can I clone from one platform to a different platform? Can I reclone just the database? Can I clone a single-node system to a multi-node system? Can I clone a multi-node system to a single-node system? What cloning options are available for each cloning method? Rapid Clone concepts Does Rapid Clone modify the source system? How does adcfgclone.pl know the target system values? What is the port pool? What if I want to give a specific value to a Server Port?
Does Rapid Clone preserve the patch history? Can I clone a clone ? Can I change the database dbfs layout while cloning? Rapid Clone and the oraInventory What is the oraInventory? What is a binary oraInventory? Is my Inventory binary? What is a XML oraInventory? Is my Inventory XML? What is the Global (or Central) Inventory? What is the Local (or Home) Inventory? How does Rapid Clone deal with the oraInventory? Why don't I need to manually copy the oraInventory when cloning? What does OUISetup.pl do?
-------------------------------------------------------------------------------Questions and Answers What is cloning? Answer: Cloning is the process of creating an identical copy of an already existing Oracle Applications system. [top]
How can I clone an Oracle Applications system? Answer: There are two cloning methods documented in the following white papers available off of Oracle MetaLink Note 135792.1
Cloning Oracle Applications Release 11i Cloning Oracle Applications Release 11i with Rapid Clone
Note: The third Cloning method (Cloning Oracle Applications Release 11i with AutoConfig) has been fully replaced by Cloning with Rapid Clone, and is no longer supported. [top]
What are the differences between the two cloning methods? Answer:
Cloning Oracle Applications Release 11i was originally published in conjunction with Release 11.5.5 and is applicable for all 11i releases up to 11.5.5 that are not AutoConfig enabled. Cloning Oracle Applications Release 11i with Rapid Clone is applicable for all 11i systems that have migrated to AutoConfig and enabled Rapid Clone. This method contains steps to install AutoConfig and Rapid Clone. [top]
What is the AD Cloning utility? Answer: AD Cloning utility (adclone.pl) is the name of the cloning command line utility. This utility is used to preserve and apply configuration information to the cloned target system. [top]
What is Rapid Clone? Answer: 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. See OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone) for instructions on installing and enabling Rapid Clone. [top]
How do I determine if my system is Rapid Clone enabled? Answer: First, verify that your system is AutoConfig enabled. Then, verify that you have applied the latest Rapid Clone patch documented in OracleMetaLink Note 230672.1 (Cloning Oracle Applications 11i with Rapid Clone). See Searching the Patch History Database in the AD Procedures Guide for instructions on searching for patches applied to your system.
[top] What is AutoConfig? Answer: AutoConfig is a configuration tool that supports automated configuration of an Oracle Applications Instance. All of the information required for configuring an Applications instance is collected into a central repository, called the Applications Context. When the AutoConfig tool runs, it uses information from the Applications Context file to generate configuration files and update database profiles. See OracleMetaLink Note 165195.1 for details on installing and migrating to AutoConfig. [top]
How do I determine if my system is AutoConfig enabled? Answer: There are several identifiers for when the system is AutoConfig enabled. The following are two common indicators: Open the environment file APPSORA.env in your APPL_TOP. If the top of the file says that it is maintained by AutoConfig, then your system is probably using AutoConfig. Check if there is an Applications Context file in the APPL_TOP/admin directory. This file will typically be named <SID>.xml or <SID>_<HOSTNAME>.xml. Check if there is an Applications Context file in the RDBMS ORACLE_HOME under the appsutil directory. This file will typically be named <SID>.xml or <SID>_<HOSTNAME>.xml. See OracleMetaLink Note 165195.1 for more details on identifying if your system already uses AutoConfig. [top] We are running Release 11.5.7 (or any prior release), which cloning method can we use? Answer: Due to the advancements in the cloning solution with Rapid Clone, all customers are now recommended to move to using Rapid Clone. if you are on release 11.5.7 or any release before 11.5.7, you will need to first enable AutoConfig on your system, if not already done, before you can use Rapid Clone as documented in the Cloning Oracle Applications Release 11i with Rapid Clone white paper. [top] We are running Release 11.5.8 (or any later release), which cloning method can we use? Answer: In 11.5.8 AutoConfig is enabled on the middle tier out of the box. In 11.5.9 and any later release, AutoConfig is enabled by default on both the database tier and the middle tier. Update AutoConfig and Rapid Clone code to the latest code line and use Rapid Clone to
clone your system. Full instructions are in Cloning Oracle Applications Release 11i with Rapid Clone document 230672.1 on OracleMetalink.
[top] Our Oracle Applications system is on Windows, which cloning method can we use? Answer: If your system is on a release prior to 11.5.7 and is not AutoConfig enabled, use the method documented in the Cloning Oracle Applications Release 11i white paper. If your system is on any AutoConfig-enabled 11i release, use the method documented in the Cloning Oracle Applications Release 11i with Rapid Clone white paper.
[top] We have a Platinum installation of Oracle Applications. Can we clone our system? Answer: Yes, cloning a Platinum system using the Rapid Clone method is no different than cloning a non-Platinum installed system. [top] Can I clone from one operating system version to another? Answer: Yes, if the target system platform is binary compatible with the source system platform. For example, if you have an existing single-node Oracle Applications system on Solaris 2.6, you could clone it to a node running Solaris 8, but not to a node running HP-UX. Note that cloning from a higher version of a platform to a lower version is not supported, for example, from Solaris 8 to Solaris 2.6. Other examples of binary compatibility for Oracle Applications are: AIX 4.3.3 to AIX 5.1 (32-bit) HP-UX 11.0 to HP-UX 11i Windows NT to Windows 2000 Within a same platform you can also clone from a 32bit source system to a 64bit target system. Note (AIX only): when cloning from AIX 32bit to AIX 64bit, apply patch 2896876 (64bit kernel extension for Oracle) on the target system prior to running adcfgclone.pl.
[top] Can I clone from one platform to a different platform? Answer: Yes, you can clone or migrate the Applications middle tier from any platform to Linux or any supported Unix platform using the procedure described in document 238276.1 "Migrating to Linux with Oracle Applications Release 11i".
[top] Can I reclone just the database? Answer: Yes, if the source system has changed and you want to update the target system with these changes, you can reclone just the changed database. If Applications patches were applied to the source system, the APPL_TOP and the database must be cloned to keep the file system and database synchronized. See the Recloning section in the white papers for details. [top] Can I clone a single-node system to a multi-node system? Answer: The Rapid Clone cloning method allows for cloning a single-node system to a multi-node system. See the Cloning Oracle Applications Release 11i with Rapid Clone white paper for details. [top] Can I clone a multi-node system to a single-node system? Answer: You can use Rapid Clone to merge multiple APPL_TOP and COMMON_TOP file systems into a single APPL_TOP and COMMON_TOP file system. For more details about this procedure, see "Section 3: Merging existing APPL_TOPs into a shared APPL_TOP" in document 233428.1 on OracleMetaLink. [top] What cloning options are available for each cloning method? Answer: The table below shows the cloning options that are currently available for each cloning method. Single node to Single node Recloning Multi-node to Multi-node Single node to Multi-node Multi-node to Single node With Oracle9i Database Windows Platform Cloning Oracle Applications Available Available Available Not Available Not Available Not Available Available Cloning Oracle Applications with Rapid Clone Available Available Available Available Available Available Available
[top] Does Rapid Clone modify the source system? Answer: No, Rapid Clone does not modify the source system. adpreclone.pl prepares the source system to be cloned by collecting information about the database and creating generic templates of files containing source specific hardcoded values. These templates are stored in the appsutil/template directory leaving the original files untouched. This process usually takes a few minutes to complete the first time. Migrating to Autoconfig on the database node (pre-req to Rapid Clone), however, will update the RDBMS init.ora and network listener files. See the instructions in the Autoconfig document 165195.1 (Section 4: Migrating to AutoConfig on the Database Tier) on how to preserve customizations to these files. [top]
How does adcfgclone.pl know the target system values? Answer: adcfgclone.pl will prompt for the values required to create the new context file used to configure the target system. A few values are calculated from the current target system (hostname, user and group). The rest of the target specific values are prompted for: Prompt Comment database SID Target database SID domain name Target system domain name Prompts specific to the DB Tier Target System database name Target System database name Target instance is a Real Application Cluster (RAC) instance (y/n) Answer yes if the target system is going to be part of a RAC instance. Current node is the first node in an N Node RAC Cluster (y/n) This prompt only appears when you answered "yes" to the previous question. Answer Â¨yes" to this question if the current host is the first node being configured in the target system RAC cluster. The tool will then ask for the number of nodes that will exist in the final RAC instance and gather, the following information for every node: - Hostname - Database Sid - Instance number - Listener port - Private interconnect name Answer "no" to this qion if at least one node of the target RAC cluster has already been configured by Rapid Clone (i.e if you already replied "yes" to this question for any other node in the cluster). The tool will then prompt for the following information to connect to a life node (the answers must describe a node that has already been configured): - Hostname
- Database Sid - Listener port RDBMS ORACLE_HOME directory Path to the Target system RDBMS ORACLE_HOME Number of DATA_TOP's: DATA_TOP 1: DATA_TOP 2: DATA_TOP 3: Database mount points. Enter the number of distinct directories containing the target database dbfs, then their paths. Prompts specific to the Apps Tier database server node hostname of the machine hosting the database server Does the target system have more than one applications tier server node (y/n)? Answer yes if the target system is part of a multi-nodes configuration. The tool with then prompt for the hostnames of: - concurrent processing node - administration node - forms server node - web server node Is the target system APPL_TOP divided into multiple mount points (y/n)? Answer yes if the target system APPL_TOP is divided across multiple mount points. The tool will then prompt for each auxiliary mount (4 mounts): - APPL_TOP mount point - APPL_TOP aux.1 - APPL_TOP aux.2 - APPL_TOP aux.3 Note: if your APPL_TOP is divided into 2 or 3 mounts only, you can specify identical mounts to the above prompts. APPL_TOP mount point APPL_TOP directory COMMON_TOP directory COMMON_TOP directory 8.0.6 ORACLE_HOME directory 8.0.6 ORACLE_HOME directory iAS ORACLE_HOME directory iAS ORACLE_HOME directory Location of JDK 1.3.1 Location of JDK 1.3.1 Prompt common to DB and Apps Tiers Port pool number:[0-99] Enter the port pool that you want to use on the target system. Make sure to specify the same port pool on the DBTier and the AppsTier. If the source and target machines are different, you have the option to preserve the source port values on the target system.
What is the port pool? What if I want to give a specific value to a Server Port?
Answer: If you are cloning on the same machine or want to redefine the server ports , you will be prompted for a port pool. The port pool provides a way to use a set of predefined server ports. There are 100 port pools. For example, if you select 3, the default database port number (1521) becomes 1524. The following table lists all the server ports. To see how the port pool calculation works, enter a number between 0 and 99(both inclusive) in the form and click "Get Ports". Port Name Autoconfig Variable (Default) Port Numbers allocated for Port Pool: 0 (Custom) Port Numbers allocated for Port Pool: Web Listener Port s_webport 8000 8001 Database Port s_dbport 1521 1522 RPC Port s_rpcport 1626 1627 Reports Port s_repsport 7000 7001 OPROC Manager Port s_oprocmgr_port 8100 8101 Web PLSQL Port s_webport_pls 8200 8201 Servlet Port s_servletport 8800 8801 Forms Listener Port s_formsport 9000 9001 Metrics Server Data Port s_metdataport 9100 9101 Metrics Server Req. Port s_metreqport 9200 9201 JTF Fulfillment Server Port s_jtfuf_port 9300 9301 iMeeting Collaboration Server Port s_imtsrvport 9500 9501 iMeeting Recording Server Port s_imtrecport 9600 9601 iMeeting Monitor (iMon) Port s_imtimonport 9700 9701 Map Viewer Servlet Port s_mapviewer_port 9800 9801 OEM Web Utility Port s_oemweb_port 10000 10001 VisiBroker OrbServer Agent Port s_osagent_port 10100 10101 MSCA Server Port s_mwaPortNo 10200 10201 MSCA Dispatcher Port s_mwaDispatcherPort 10300 10301 TCF Port s_tcfport 15000 15001 OACORE Servle Port Range s_oacore_servlet_portrange 16000-16009 16010-16019 Discoverer Servlet Port Range s_disco_servlet_portrange 17000-17009 17010-17019 Forms Servlet Port Range s_forms_servlet_portrange 18000-18009 18010-18019 XMLSVCS Servlet Port Range s_xmlsvcs_servlet_portrange 19000-19009 19010-19019 Forms Start Port s_frmStartPort 20000 20001 Java Object Cache Port s_java_object_cache_port 12345 12346
If you want to give a specific value to a port on the target system, independently from the port pool, you must first complete the Target System configuration with adcfgclone.pl (temporarily select a value for the port pool). Once adcfgclone.pl completes successfully, edit the new target context file with editcontext or OAM and modify the corresponding Autoconfig variables. Run Autoconfig to refresh the system with the new values (see OracleMetaLink document 165195.1). [top]
Does Rapid Clone preserve the patch history? Answer: Yes, Rapid Clone preserves the patch history of the complete Applications Stack: RDBMS ORACLE_HOME: preserve the OUI oraInventory. iAS ORACLE_HOME: preserve the OUI oraInventory. 806 ORACLE_HOME: preserve the patch level and ORCA inventory. APPL_TOP and Database: preserve the patch level and history tables. [top]
Can I clone a clone? Answer: Yes, a cloned system created with Rapid Clone can then be used as the Source System in the next cloning. RapidInstall itself is now a clone of a clone using the Rapid Clone technology. [top]
Can I change the database dbf files layout while cloning? Answer: Yes, Rapid Clone allows to add or remove database mount points or redidtribute dbf files among mount points in the target system. As long as all the source system dbf files are present in the target system database mount points specified during the adcfgclone prompts (see question "How does adcfgclone.pl know the target system values?"), Rapid Clone will find them and re-create the database control file accordingly. [top]
What is the oraInventory? Answer: The oraInventory is the location for the OUI (Oracle Universal Installer)'s bookkeeping. The inventory stores information about: All Oracle software products installed in all ORACLE_HOMES on a machine Other non-Oracle products, such as the Java Runtime Environment (JRE) In a 11i Application system the RDBMS and iAS ORACLE_HOMEs are registered in the oraInventory. The 806 ORACLE_HOME, which is not managed through OUI, is not. On Unix/Linux, the location of the oraInventory is defined by the content of oraInst.loc, at: - /var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX On Windows, the location of the oraInventory is defined by the value of the registry key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\Program Files\Oracle\Inventory [top]
What is a binary oraInventory? Is my Inventory binary? Answer: Before OUI 2.X, the oraInventory was binary. A binary oraInventory centralizes, in a binary format, the location of every Oracle products on the machine and the detail of their patch level. The oraInventory location is defined by the content of oraInst.loc. You will have a binary inventory only if ALL of the following conditions are met:
you are on 11.5.7 or earlier (11.5.8+ install XML inventory out of the box) you have never installed OUI 2.X or higher (Install converts the inventory to XML) you have never run Rapid Clone (Rapid Clone converts the inventory to XML) If the following file exists, the oraInventory is NOT binary: <oraInventory location as pointed by oraInst.loc>/ContentsXML/inventory.xml [top]
What is a XML oraInventory? Is my Inventory XML? Answer: Starting with OUI 2.X and 11.5.8, the information in the inventory is stored in Extensible Markup Language (XML) format. The XML format allows for easier diagnosis of problems and faster loading of data Rapid Clone requires the inventory to be in XML format in order to clone it, and will take care of performing the binary to XML convertion if necessary. Unlike the binary oraInventory, The XML inventory is divided into 2 distinct components:
The Global inventory (or Central inventory) The Local inventory (or Home inventory) More information about these components is available under other questions in this FAQ The inventory is XML if the following file exists: $ORACLE_HOME/inventory/ContentXML/comps.xml [top]
What is the Global (or Central) Inventory? Answer: The Global Inventory is the part of the XML inventory that contains the high level list of all oracle products installed on a machine. There should therefore be only one per machine. Its location is defined by the content of oraInst.loc. The Global Inventory records the physical location of Oracle products installed on the machine, such as ORACLE_HOMES (RDBMS and IAS) or JRE. It does not have any information about the detail of patches applied to each ORACLE_HOMEs. The Global Inventory gets updated every time you install or de-install an ORACLE_HOME on the machine, be it through OUI Installer, Rapid Install, or Rapid Clone. Note: If you need to delete an ORACLE_HOME, you should always do it through the OUI de-installer in order to keep the Global Inventory synchronized. [top]
What is the Local (or Home) Inventory? Answer: There is one Local Inventory per ORACLE_HOME. It is physically located inside the ORACLE_HOME at $ORACLE_HOME/inventory and contains the detail of the patch level for that ORACLE_HOME. The Local Inventory gets updated whenever a patch is applied to the ORACLE_HOME, using OUI. [top]
How does Rapid Clone deal with the oraInventory? Answer: Rapid Clone requires OUI 2.2 to be installed in the ORACLE_HOME as a prerequisite and will performs all the actions necessary to clone the inventory:
Converts the Global inventory to xml format when it was binary on either the source system or the target system Registers the cloned ORACLE_HOME in the target system Global Inventory Updates the Local Inventory of the target ORACLE_HOME to reflect the new machine, paths, users, etc. [top]
Why don't I need to manually copy the oraInventory when cloning? Answer: The local inventory is automatically copied from the source system to the target system as part of copying the ORACLE_HOME itself.
The Global Inventory is machine specifc and therefore should not be copied. If you are cloning from one machine to a different machine, Rapid Clone will simply register the target ORACLE_HOME in the target machine Global Inventory (This action will automatically create the Global Inventory if it did not exist on that machine). [top]
What does OUISetup.pl do? Answer: OUISetup.pl is shipped with the OUI patch, listed as a prerequisit to Rapid Clone (see Metalink Node 230672.1). It should be run as part of the OUI patch installation and will perform the following tasks:
Register the OUI program in the Global Inventory Register the JRE in the Global Inventory Ensure that the ORACLE_HOME in which the patch is install is properly registered in the Global Inventory. In doing so, it will attempt to automatically fix Inventory corruptions that are known to cause problem whilie cloning, such as - Home indexes out of sync between the Global and Local Inventory - Duplicate Home Names entries - Duplicate Home Path entries