EBS 11i Creating a Clone using Oracle Application Manager (OAM Clone)
(Doc ID 398619.1)
Last updated on NOVEMBER 07, 2016
Oracle Applications Manager - Version 126.96.36.199 to 188.8.131.52 [Release 11.5.10] Information in this document applies to any platform.
Checked for relevance on 22-DEC-2013
Creating a duplicate of an Oracle Applications system is required for several reasons. For Example:
Create a copy of a production system to use for testing updates
Create a staged system to reduce downtime associated with the patching process
However, creating a duplicate system cannot be done by simply copying all the Oracle Applications components. There are numerous configuration files in the file system that must be modified, depending on the physical configuration of the target environment. Additionally, the Oracle Applications installation process uses the Oracle Universal Installer (OUI), which maintains key information about the installation in an inventory. Copying this installation to a new location would invalidate this information, preventing the application of patches to components that are maintained by the Installer.
To create a working duplicate, the existing system must be cloned. Cloning creates an identical copy, including component versions, operating system, and platform type — it is a fully functional copy of the existing system.
Oracle Applications 11i can be cloned via two methods, RapidClone or Oracle Applications Manager Cloning (OAM Clone) For information on RapidClone refer to <Note:230672.1>.
This document provides information on Oracle Application Manager Cloning and is an enhancement of the existing information regarding cloning in 11i OAM Online help.
The Oracle Applications Manager Cloning methodology combines AutoConfig processing with OAM Rapid Clone features to create and configure the duplicate system. Oracle Applications Manager Cloning was introduced via either of the following patchsets: