In this post we are going to cover 10 key points of Oracle Apps DBA (R12) Cloning. For those who are new with Cloning, it is the process of creating a copy of an existing Oracle E-Business Suite system. Cloning is one the most common task that AppsDBA do.
For Database cloning in R12 using RMAN backup, please refer our previous post: Oracle EBS (R12): Database Cloning from RMAN backup
If you are new to Oracle AppsDBA or already working as Apps DBA but on version 11i or R12.1 then suggest you first go through with below FREE videos on EBS R12.2 from Oracle ACE, Author, and Oracle Apps Expert Atul Kumar
- [Video] Oracle Apps DBA (R12.2) Architecture
- [Video] Oracle Apps DBA (R12.2) Installation: FREE Training
- [Video] File System in Oracle E-Business Suite R12.2: Dual, APPL_TOP, INST_TOP, COMMON_TOP, FMW_HOME
- [Video] Oracle Apps DBA (R12.2) Services: Start/Stop
- [Video] Oracle Apps DBA (R12.2) Patching (ADOP): FREE Training
10 Key Points of Oracle AppsDBA (R12) Cloning
1. An Oracle E-Business Suite system can only be cloned to the same, or a higher, major release of a platform (operating system).
For example, you can clone a system running on Oracle Solaris 10 to run on Oracle Solaris 11, but it is not supported to clone a system running on Solaris 11 to run on Solaris 10.
2. In AD-TXK Delta 7, Oracle recommend you clone the Application tier run and patch file systems in a single operation, using the ‘dualfs’ option. Separate cloning of the run and patch file systems will be deprecated in the future
3. Cloning can be done to Same or Higher release of Platform (You can’t clone from Linux to Solaris or Windows)
4. Standard cloning is different from file system cloning. Standard cloning is creating a copy of an Oracle E-Business Suite system using Rapid Clone (for example, cloning a complete Oracle E-Business Suite system to create a test copy from your production environment). In contrast, file system cloning is copying the run file system to the patch file system in online patching, and can only be undertaken with the
adop phase=fs_clone command.
5. When cloning, ensure that you specify the actual locations for the directories involved, so that AD utilities can properly identify the directories afterward. Do not use symbolic links to specify directory locations.
6. Before cloning a system with Rapid Clone, be sure to allow any active online patching cycles to run all the way through the final (cleanup) phase. In case patches are applied in hotpatch or downtime mode, then you must run
cleanup phase of
7. Then run
fs_clone to synchronize with the other file system, to avoid the need for synchronization to be performed in the next patching cycle.
8. A global (central) inventory is generally recommended for all Oracle E-Business Suite Release 12.2 application tier nodes and database tier nodes.
However, starting AD/TXK.Delta.7, support for using an ‘EBS Installation Central Inventory’ has also been introduced for Application tier. This inventory will be specific to an E-Business Suite instance and will be identified by ‘<s_base>/oraInventory/oraInst.loc’.
9. If your system has separate installation user accounts for the database and the applications, both users must be in the same install group (inst_group) in oraInst.loc, which will need to contain a line such as inst_group=oracle.
10. In Release 12.2, you can set the base directory to any desired location. However, the subdirectory structure cannot be changed because of dependencies on both the WLS domain and the dual file system required for online patching. Also, the base directory must be the same across all nodes in multi-node configurations.
- Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)
- Multi Node Cloning Oracle E-Business Suite Release 12.2 (Doc ID 1375769.1)
- Cloning Oracle E-Business Suite Release 12.2 Environments integrated with Oracle Access Manager 11gR2 (11.1.2) (Doc ID 1614793.1)
This post is from our Oracle Apps DBA (R12.2) Training, in which we cover Architecture & Changes in Oracle E-Business Suite R12.2, Staging & Installation, File System & Important Files in R12.2, Start/Stop, Patching, AD Administration, Cloning, Concurrent Managers, AutoConfig, Password Management and Troubleshooting and much more.
Next task for you
Download Your Free Guide by clicking on the below image down learn Cloning in EBS R12 for Apps DBA
Are you having any queries or hitting any issues in R12.2 cloning?
If you like this post then don’t forget to share with your Apps DBA Friends