Cloning Oracle Applications

Cloning Oracle Applications Release 11i

with Rapid Clone

May 2011

Cloning creates an identical copy of an existing Oracle Applications System. There are various reasons for cloning an Oracle Applications System such as:

• • Creating a copy of the production System for testing updates.

  • Migrating an existing System to new hardware.

  • Creating a stage area to reduce patching downtime.

This document describes the process of cloning an Oracle Applications Release 11i System. The most current version of this note is document 230672.1 on My Oracle Support. A FAQ is also available indocument 216664.1 on My Oracle Support.

Note: Rapid Clone is currently not supported on HP OpenVMS Alpha.

Attention: Windows users. This document typically uses UNIX syntax when specifying directories; Please substitute the appropriate Windows syntax

Note: The Cloning methodology posted on this document requires full Autoconfig compliance.

• • Section 1: Prerequisites

  • Tasks to perform before using Rapid Clone.

  • Section 2: Clone Oracle Applications 11i

  • Tasks to prepare, copy, configure, and verify a cloned Applications System.

• Section 3: Finishing Tasks

  • Tasks to complete the cloning process.

  • Section 4: Advanced Cloning Methods

  • Tasks for advanced options such as refreshing and Multi-Node cloning.

Conventions

• • • • • 1. Attention: Every time that a new Rapid Clone or Autoconfig patch is applied on the APPL_TOP, the RDBMS ORACLE_HOME must be updated with the files included on those patches.

          2. Follow the instructions in section Maintaining System Configuration in document 165195.1 on My Oracle Support to synchronize the Rapid Clone and Autoconfig files on the RDBMS ORACLE_HOME.

1. Maintain Snapshot information

   1. Log in to each Application Tier Node as the APPLMGR user and run Maintain Snapshot information in AD Administration.

   2. See Oracle Applications Maintenance Utilities for more information.

Section 2: Clone Oracle Applications 11i

Use Rapid Clone to create template files for cloning on the Source System. After the Source System is copied to the target, Rapid Clone updates these templates to contain the new target System configuration settings. Rapid Clone will not change the Source System configuration.

There are three phases to the cloning process:

1. Prepare the Source System

   1. Execute the following commands to prepare the Source System for cloning.

      1. 1. Prepare the Source System Database Tier for cloning

         2. Log on to the Source System as the ORACLE user and run the following commands:

         3. cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]

         4. perl adpreclone.pl dbTier

         5. Prepare the Source System Application Tier for cloning

         6. Log on to the Source System as the APPLMGR user and run the following commands on each Node that contains an APPL_TOP:

         7. cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]

         8. perl adpreclone.pl appsTier

2. Copy the Source System to the Target System

• 1. Copy the Application Tier File System from the Source Applications System to the Target Node by executing the following steps in the order listed. Ensure the Application Tier files copied to the Target System are owned by the Target APPLMGR user, and that the Database Tier files are owned by the ORACLE user.

     1. Copy the Application Tier File System

        1. Log on to the Source System Application Tier Nodes as the APPLMGR user.

           1. • Shut down the Application Tier Server processes

              • Copy the following Application Tier directories from the Source Node to the Target Application Tier Node:

                • [APPL_TOP]

                • [OA_HTML]

                • [OA_JAVA]

                • [OA_JRE_TOP]

                • [COMMON_TOP]/util

                • [COMMON_TOP]/clone

                • [COMMON_TOP]/_pages (when this directory exists)

                • [806 ORACLE_HOME]

                • [iAS ORACLE_HOME]

     2. Copy the Database Tier File System

• • • 1. Log on to the Source System Database Node as the ORACLE user.

         1. • Perform a normal shutdown of the Source System Database

            • Copy the Database (DBF) files from the Source to the Target System

            • Copy the Source Database ORACLE_HOME to the Target System

            • Start up the Source Applications System Database and Application Tier processes

• • • • • 1. Note: Unix/Linux users, make sure that the softlinks are preserved when copying. Additionally, verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root (i.e. nmo, nmhs, nmb, etc).

1. Configure the Target System

   1. Execute the following commands to configure the Target System. You will be prompted for the Target System specific values (SID, Paths, Ports, etc).

      1. Configure the Target System Database Server

         1. Log on to the Target System as the ORACLE user and type the following commands to configure and start the Database:

            1. cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

            2. perl adcfgclone.pl dbTier

      2. Configure the Target System Application Tier Server Nodes

• • • 1. Log on to the Target System as the APPLMGR user and type the following commands:

         1. cd [COMMON_TOP]/clone/bin

         2. perl adcfgclone.pl appsTier

Section 3: Finishing Tasks

This section lists tasks that may be necessary depending on your implementation and the intended use of the cloned System.

1. Update profile options

   1. Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually.

2. Update printer settings

• 1. If the new cloned System needs to utilize different printers, update the Target System with the new printer settings now.

3. Update workflow configuration settings

• 1. Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the Target System.

1. Verify the APPLCSF variable setting

   1. Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to an acceptable directory. To modify it, change the value of s_applcsf in the contextfile and run AutoConfig.

2. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS

• 1. If the Target System is in a different domain name than the Source System andSESSION_COOKIE_DOMAIN was not null in the Source System, update that value to reflect the new domain name.

3. Re-Implement SSL and SSO configuration

• 1. If the Source System was SSL or SSO enabled, and the Target is wished to be SSL or SSO enabled, then reconfigure the Target by following the SSL/SSO documentation. Otherwise, if the Target is wished to be non-SSL or non-SSO, then follow the same SSL/SSO documentation to undo the SSL/SSO setup.

4. Windows users only reboot the Target machine

• 1. Once cloning is completed reboot to enable the services.

Section 4: Advanced Cloning Options

This section describes advanced cloning procedures.

1. Refreshing a Target System

   1. You may need to refresh the Target System periodically to synchronize it with changes from the Source.

• • • • • 1. Attention: Backup the Target Context File on the Target System before refreshing the dbTier or appsTier.

• • 1. To refresh the Target System, perform the following steps as described in previous sections:

    2. Prepare the Source System

    3. Copy the Source System to the Target System

       1. • Copy the Application Tier File System if the APPL_TOP, 806 ORACLE_HOME, or iAS ORACLE_HOME needs to be refreshed. Copy the portion of the Application Tier File System which has been updated.

          • 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.

    4. Configure the Target System

• • • 1. Specify the existing Target System Context File when running adcfgclone.pl commands:

         1. 1. cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

            2. perl adcfgclone.pl dbTier [Database Target Context File]

               1. Where Database Context File is:

               2. [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml

            3. cd [COMMON_TOP]/clone/bin

            4. perl adcfgclone.pl appsTier [Appltop Target Context File]

• • • • • • 1. Where Appltop Context File is:

            2. [APPL_TOP]/admin/[Target CONTEXT_NAME].xml

• • 5. Finishing Tasks

1. Cloning a Single-Node System to a Multi-Node System

   1. This procedure allows the original Single-Node System to be cloned into a Multi-Node System. An Applications System comprises five Server types:

      1. • Database Server (Database Tier)

         • Forms Server (Application Tier)

         • Web Server (Application Tier)

         • Concurrent Processing Server (Application Tier)

         • Administration Server (Application Tier)

• • 1. During the Single-Node to Multi-Node cloning process, each of these Servers can be placed on its own Node, resulting in a Multi-Node Target System.

    2. Perform prerequisites

       1. Perform these steps on all Source and Target Nodes.

    3. Clone Oracle Applications 11i

• • • 1. 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. You can specify the Server type for each Target Node while answering the prompts during the configuration step.

      2. The Database ORACLE_HOME and Database only need to be copied to the Node on which the Database will be run.

• • 4. Finishing Tasks

1. Cloning a Multi-Node System to a Multi-Node System with same number of Nodes

   1. A Multi-Node System can be cloned provided the number of Nodes and distribution of Servers in the Target System matches that of the Source System.

      1. 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.

1. Adding a new Node to an existing System

   1. You can use Rapid Clone to clone a Node and add it to the existing Application System. The new Node will run the same or a subset of the Server types running on the Source Node. Follow the instructions in the Application Tier part of Clone Oracle Applications 11i:

      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

1. Reducing the number of Nodes of a Multi-Node System (merge APPL_TOP)

   1. You can 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_TOPs fileSystem together. Follow the procedure for Merging existing APPL_TOPs in document 233428.1 on My Oracle Support.

2. Cloning a RAC System

• 1. You can use Rapid Clone to clone a RAC System. While cloning, you have the possibility to remove or add Nodes to the cluster in the Target RAC System.

• • 1. To clone a RAC System, perform the following tasks:

       1. Verify the prerequisites

          1. • Apply TXK patch 3571388 (AutoConfig support for Oracle RAC instances)

             • Migrate the Source System cluster ORACLE_HOMES to AutoConfig as documented in document 165195.1 on My Oracle Support

    2. Prepare the Source System

• • • 1. Choose one of the ORACLE_HOMEs on the Source cluster. This ORACLE_HOME will be used as a master to create all the Target cluster System ORACLE_HOME. Run "perl adpreclone.pl dbTier" on it.

1. Adding a Node to an existing RAC Cluster

   1. You can use Rapid Clone to add one or several Nodes to an existing RAC Cluster.

• • 1. Perform the following tasks:

       1. Choose any one of the ORACLE_HOMEs in the existing cluster and run the following command:

          • cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

          • perl adcfgclone.pl dbTier

       2. This ORACLE_HOME will be used as a master to create the additional Node(s).

       3. Copy the master ORACLE_HOME File System to the new Node(s).

       4. On the init.ora, set the variable "cluster_Database_instances" to match the new number of Nodes.

• • • • • • When instructed so by the previous step, log on to every Node from the original cluster and run the following command on each of them:

            • cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

            • perl adcfgclone.pl addracNode [Context File]

          • Go back to the first Node and complete adcfgclone.pl

          • If you are adding more than one Node to the original cluster, log on to each of the remaining new Nodes and run

            • • cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

              • perl adcfgclone.pl dbTier

1. Cloning a Shared File System

   1. You can use Rapid Clone to clone a shared APPL_TOP System. Since all the Nodes share a unique APPL_TOP you only need to fully clone one of the Source System Nodes to its Target machine and add more Nodes directly sharing the APPL_TOP on the Target System. Choose one of the shared APPL_TOP Nodes on Source System (the rest of this section will refer to it as Node A) and perform the following tasks:

      1. Perform prerequisites

         1. Perform these steps on Node A and and every Target Nodes.

      2. Clone Oracle Applications 11i

• • • 1. Perform a full clone (Prepare, copy and configure steps) of the Database Tier and Node A (Application Tier).

1. 1. 3. Add the shared File System Nodes to the Target System

• • • 1. On the Target System, follow the instructions for adding a Node to a shared APPL_TOP System in document 233428.1 on My Oracle Support and add more Nodes sharing the Target System APPL_TOP to match the Source System topology.

Appendix A: Install JRE 1.3.1 into RDBMS ORACLE_HOME

Windows customers will need to perform the following steps:

• • Download JRE 1.3.1 from Sun MicroSystems.

  • Run the install executable

  • When prompted for the location to install jre, click browse and enter the location: [RDBMS ORACLE_HOME]\jre\1.3.1

  • Accept the default installation options.

JRE 1.3.1 will be installed into the [RDBMS ORACLE_HOME]\jre\1.3.1 directory.

Appendix B: Recreating Database control files manually in Rapid Clone.

This Appendix documents the steps to allow manual creation of the Target Database control files within the Rapid Clone process. Examples of when to use this method are for Databases on raw partitions or hot backup cloning. Replace section 2.3a (Configure the Target System Database Server) with the following steps:

• • Log on to the Target System as the ORACLE user

  • Configure the [RDBMS ORACLE_HOME>

    • cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

    • perl adcfgclone.pl dbTechStack

  • Create the Target Database control files manually

  • Start the Target System Database in open mode

  • Run the library update script against the Database

    • cd [RDBMS ORACLE_HOME]/appsutil/install/[CONTEXT NAME]

    • sqlplus "/ as sysdba" @adupdlib.sql [libext]

    • Where [libext] should be set to 'sl' for HP-UX, 'so' for any other UNIX platform,

    • or 'dll' for Windows.

  • Configure the Target Database (the Database must be open)

    • • cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

      • perl adcfgclone.pl dbconfig [Target Context File]

      • Where Target Context File is:

      • [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml