• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
R12 d49656 gc10-apps dba 27
 

R12 d49656 gc10-apps dba 27

on

  • 1,392 views

Oracle Applications, Oracle Database, D49656, Oracle Applications DBA

Oracle Applications, Oracle Database, D49656, Oracle Applications DBA

Statistics

Views

Total Views
1,392
Views on SlideShare
1,392
Embed Views
0

Actions

Likes
1
Downloads
113
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • ILT Schedule: Timing Topic 20 minutes Lecture 0 minutes Practice 20 minutes Total
  • -
  • - 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.
  • -
  • -
  • -
  • -
  • -
  • 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.
  • -
  • - 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.
  • - Prepare the Source System Perform these steps as detailed in the Cloning Oracle Applications module.
  • - 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.
  • - Configure the Target System See details for the Configure the Target System steps in the Cloning Oracle Applications module.
  • -
  • -
  • -
  • -
  • - 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.
  • -
  • - Cloning a Multi-node System to a Multi-node System Note: The database server node must always be cloned first.
  • -
  • -
  • -
  • -

R12 d49656 gc10-apps dba 27 R12 d49656 gc10-apps dba 27 Presentation Transcript

  • Advanced Cloning Options
  • Objectives
    • At the end of this module, you should be able to do the following:
      • Refresh a cloned target system
      • Clone a single-node system to a multi-node system
      • Clone a multi-node system to a multi-node system
      • Add a node to an existing system
      • Reduce the number of nodes on a multi-node system
  • Module Overview
    • This module consists of the following topics:
      • Refresh a cloned target system
      • Clone a single-node system to a multi-node system
      • Clone a multi-node system to a multi-node system
      • Add a node to an existing system
      • Reduce the number of nodes on a multi-node system
  • Advanced Cloning Options
      • Advanced cloning options include:
      • Refreshing a target system
      • Cloning multi-node systems
      • Adding a new node to an existing system
  • Refreshing a Target System
    • You may need to refresh a target system periodically to synchronize it with changes made on the source system
      • Prepare the source system (as described previously)
  • Refreshing a Target System
      • Copy any parts of the application tier file system that have been updated on the source system
        • The APPL_TOP, COMMON_TOP, or technology stack may need to be refreshed on the target system
      • Copy the database node file system if the RDBMS_ORACLE_HOME or database need to be refreshed
        • If refreshing the database, refresh the RDBMS_ORACLE_HOME at the same time
  • Refreshing a Target System
      • Configure the target system to be refreshed by specifying the existing target system when running adcfgclone commands:
    perl adcfgclone.pl dbTier <Database tier context file on target> perl adcfgclone.pl appsTier <INST_TOP/appl/admin/<Application tier context file on target>
  • Refreshing a Target System
      • Where applicable, carry out the finishing tasks described earlier
    Source Target
  • Cloning Multi-Node Systems
    • You can use Rapid Clone in cases where the source or target system has a multi-node application tier
      • With Release 12, only one copy of the files for the application tier nodes needs to be copied to the target system, regardless of shared file system usage
    Source Target Multi-Node Application Tier (Shared File System)
  • Cloning Multi-Node Systems
      • Details of adding shared file system application tier nodes are described in Oracle MetaLink Note 384241.1
      • If adding non-shared nodes, the copy and configure steps must be performed as on the primary node
    Source Target Multi-Node Application Tier (Non-Shared File System)
  • Adding a New Node to an Existing System
      • You can also use Rapid Clone to set up a new node being added to an existing Applications system
      • The new node can either run the same services as the source node, or different services
      • Prepare the source system, copy it to the new node and configure it as applicable
      • After adcfgclone completes, set up the environment and run the following commands on the target system:
    cd <COMMON_TOP>/clone/bin perl adaddnode.pl
  • Refresh a Cloned Target System
      • Prepare the source system
      • Copy the source system to the target system
      • Configure the target system
      • Perform finishing tasks
    Source Target
  • Prepare the Source System
      • Prepare the source system database tier for cloning
      • Prepare the source system application tier for cloning
    Source Target
  • Copy the Source System to the Target System
      • Copy the application tier file system if the APPL_TOP, OracleAS 10.1.2 ORACLE_HOME, or OracleAS 10.1.3 ORACLE_HOME needs to be refreshed
        • Copy the updated portion of the application tier file system
      • Copy the database tier file system if the RDBMS ORACLE_HOME or the database needs to be refreshed
        • If refreshing the database, the ORACLE_HOME should be refreshed at the same time
    Source Target
  • Configure the Target System
    • Specify the existing target system context file when running adcfgclone.pl commands:
    • where database context file is: <RDBMS ORACLE_HOME>/appsutil/ <Target CONTEXT_NAME>.xml
    • where application tier target context file is: <INST_TOP>/appl/admin/<Target CONTEXT_NAME>.xml
    perl adcfgclone.pl dbTier <Database target context file> perl adcfgclone.pl appsTier <Application tier target context file>
  • Finishing Tasks
      • Update profile options
        • Rapid Clone updates only site-level profile options
        • If any other profile options are set to instance-specific values, you must update them manually
      • Update printer settings
        • If the new cloned system utilizes different printers, update the target system with the new printer settings
      • Update Workflow and other configuration settings
        • Cloning an instance will not update the host- and instance-specific information used by Oracle Workflow and other components
        • Refer to the following slides to confirm there is no instance-specific data on the target system
  • Clone a Single-Node System to a Multi-Node System
      • This procedure allows the original single node system to be cloned into a multi-node system
  • Clone a Single Node System to a Multi-Node System
    • Perform the following sections from the Cloning Oracle Applications module to clone a single-node system to multi-node system:
      • Perform prerequisites
      • Clone Oracle Applications
      • Finishing Tasks
  • Prerequisite Steps
    • Perform the following prerequisite steps on the source and all target nodes:
      • 1. Verify source and target nodes software versions
      • 2. Apply the latest Rapid Clone patch (if applicable)
      • 3. Set up Rapid Clone on the application tier
      • 4. Set up Rapid Clone on the database tier
  • Clone Oracle Applications
    • There are three phases to the cloning process:
      • Prepare the source system
      • Copy the source system to the target system
      • Configure the target system
    Source Target Prepare Copy Configure
  • Finishing Tasks
      • Update profile options
      • Update printer settings
      • Update Workflow and other configuration settings
    Source System Target System
  • Cloning a Multi-Node System to a Multi-Node System
      • A multi-node system can be cloned if the number of nodes and distribution of servers in the target system matches that of the source system
      • To clone a multi-node system to a multi-node system, perform the cloning process on each node
      • For example, if the source system contains three nodes, perform the cloning process three times:
        • Clone source system node 1 to target system node 1
        • Clone source system node 2 to target system node 2
        • Clone source system node 3 to target system node 3
  • Adding a Node
      • Use Rapid Clone to clone a node and add it to the existing Application System
      • Follow the instructions in the Application Tier part of Cloning Oracle Applications Release 12 (Oracle MetaLink Note 406982.1):
        • Prepare the source system, copy it to the new node and configure it
        • After adcfgclone.pl completes, source the Applications environment and run the following commands on the target system:
            • cd <COMMON_TOP>/clone/bin
            • perl adaddnode.pl
  • Reducing the Number of Nodes
      • Reduce the number of nodes of a multi-node system by merging the APPL_TOPs
      • Use Rapid Clone to clone a multi-node system to a single-node system (or a multi-node system with fewer nodes) by merging the APPL_TOP file systems
  • Module Summary
    • In this module, you should have learned how
    • to do the following:
      • Refresh a cloned target system
      • Clone a single-node system to a multi-node system
      • Clone a multi-node system to a multi-node system
      • Add a node to an existing system
      • Reduce the number of nodes on a multi-node system
  • Module Discussion
      • Name some situations that may require refreshing a cloned Oracle Applications system
      • When cloning a single-node system to a multi-node, what are the limitations on the number of nodes?