ILT Schedule: Timing Topic 20 minutes Lecture 0 minutes Practice 20 minutes Total
<Course name> <Lesson number> -
<Course name> <Lesson number> - Overview The following terms are used to identify the systems: Source system - the system to be cloned. Target system - the newly created (or cloned) system.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
Cloning Multi-Node Systems Rapid Clone can be used where the source system or target system is a multi-node system. As of Release 12, all APPL_TOPs are unified APPL_TOPs: that is, all files required for all application tier services are included with every Applications node, with multiple nodes being differentiated by the services started on each. Therefore, only one copy of the Applications node files needs to be copied to the target system, regardless of whether a shared file system is being used on the source or target system. To add shared Applications nodes on the target system, follow the instructions in OracleMetaLink Note 384241.1, Sharing the Application Tier File System in Oracle E-Business Suite Release 12 . To add non-shared Applications nodes, carry out the copy and configure steps in the same way as on the primary node. You can specify the services to start for each target Applications node while answering the prompts during the configuration step. Instructor Note: Support for use of Rapid Clone with Oracle RAC (Real Application Clusters) is planned for a future release of Oracle Applications.
Cloning Multi-Node Systems To add shared application tier nodes on the target system, follow the instructions in OracleMetaLink Note 384241.1, Sharing the Application Tier File System in Oracle E-Business Suite Release 12. To add non-shared application tier nodes, carry out the copy and configure steps in the same way as on the primary node. You can specify the services to start for each target Applications node when answering the prompts during the configuration step.
<Course name> <Lesson number> -
<Course name> <Lesson number> - Refresh a Cloned Target System You may need to refresh the target system periodically to synchronize it with changes from the source system. To refresh the target system, perform the steps listed on this slide.
<Course name> <Lesson number> - Prepare the Source System Perform these steps as detailed in the Cloning Oracle Applications module.
<Course name> <Lesson number> - Copy the Source System to the Target System See details for the Copy the Source System to the Target System steps in the Cloning Oracle Applications module.
<Course name> <Lesson number> - Configure the Target System See details for the Configure the Target System steps in the Cloning Oracle Applications module.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - Clone Oracle Applications Prepare, copy and configure the cloned Applications System. When creating more than one application tier server node from a single node system, the copy and configure steps must be performed on each target node. The database ORACLE_HOME and database only need to be copied to the node on which the database will be run.
<Course name> <Lesson number> -
<Course name> <Lesson number> - Cloning a Multi-node System to a Multi-node System Note: The database server node must always be cloned first.