Oracle Application Management Pack for Oracle E-Business Suite Guide Release 12.1.0.1.0 Part Number E28715-03

Contents

Previous

Next

Cloning an Oracle E-Business Suite System

Cloning an Oracle E-Business Suite System

One of the key features of the Oracle Application Management Pack for Oracle E-Business Suite is the ability to clone an Oracle E-Business Suite system automatically using the Smart Clone procedure.

The key highlights of the cloning process include:

• The Oracle Application Management Pack for Oracle E-Business Suite allows Oracle E-Business Suite systems to be cloned using the Cloud Control provisioning framework.

• Cloud Control automates the creation of clone systems and executes any required application-specific actions.

• Cloning of systems deployed on Oracle Real Application Clusters (RAC) is possible. For more information, see the My Oracle Support Knowledge Documents listed later in this section.

Smart Clone

Smart Clone allows you to use the database target cloned using external third-party solutions as an input to its deployment procedures. Smart Clone procedures would take this input to configure a database target and then clone the applications tier of the source instance and then apply that to the target Oracle E-Business Suite system.

Smart Clone supports the following scenarios for both Release 11i and Release 12:

• Configuring single instance databases

• Configuring RAC databases

  • Customizing the listener names is supported if you have the required Oracle E-Business Suite patches applied.

  • Listeners can also be configured with Scan IPs

For both Release 11i and Release 12:, the following applications tier cloning and configuration procedures are supported:

• Single Node to Single Node

• Multi-Node to Single Node (Scale Down)

In addition to the above features, the following scenarios are supported:

• As soon as Oracle E-Business Suite announces the certification on any database version with Oracle E-Business Suite, then the Oracle Application Management Pack for Oracle E-Business Suite (Release 12.1.0.1.0) customers should be able to use the Smart Clone deployment procedure immediately for Oracle E-Business Suite cloning.

• Any specific needs like data masking, data compression, and so on can be performed before running Smart Clone.

• Smart Clone supports cloning of systems with different OS users for the database tier and the applications tier

Terms

The following table lists some cloning terms used in this document.

Additional Setup Steps

• Cloning using Oracle Application Management Pack for Oracle E-Business suite requires Perl 5.005 or higher on the Oracle Enterprise Manager agent. The user who starts the agent processes must set the PERL5LIB environment variable pointing to Perl 5.005 (or higher) libraries. Also, the Perl executable 5.005 must be used.

• While upgrading the database from 9i to 10g (or 11g) with and Oracle E-Business Suite Release 11i instance, you need to ensure that the source instance perl.exe is pointed to the database 10g (11g) ORACLE_HOME of the Oracle E-Business Suite.

• All the virtual internet protocol (VIP) addresses configured in the Oracle Cluster Ready Services (CRS) of the targets nodes identified for the created RAC instance must be up and running.

• With Release 11i, for a clone job from Single Node - Single User to Single Node - Multiple User, ensure that you have write permissions for user IDs to the target base directory. Give 770 permissions to the directories from/to the target base directory with the following command:

  $ chmod -R 770 <target base directory>

• If for a cloning process the target is multi-node and the database node domain and the applications node domain are different, perform the following step:

  1. Include the target database node server name in the /etc/hosts file of the target applications node so that the applications node will be able to resolve the database node without the domain name. The modification should be like the following (this entry is for Linux x86; change as appropriate for your platform):

     <ip-address> <Machine name with domain name> <Machine Name>

     For example:

     140.87.205.217 adc60002demo.us.oracle.com adc60002demo

  2. For Release 12 only: In addition to the above entry in the /etc/hosts file, the applications node context file needs to be changed.

     Change the s_dbdomain entry in the <STAGE_LOC>/appsTier/context/apps/<SID>_<SERVER_NAME>.xml file to the correct domain name of the database tier.

     For example, if the database node domain name is idc.oracle.com, and the applications node domain name is us.oracle.com, then the context file

     /d1/QA/stage/PMS29/080522035852/PMS29_adc60010demo.xml

     should be changed to

     <domain oa_var="s_dbdomain">idc.oracle.com</domain>

• The OS utilities make, ld, cc, and ar must be in the environment PATH variable in all the host targets. If not, please update the PATH variable accordingly and restart the agent in the same terminal.

Cloning with RAC Instances

With Smart Clone, if the target Oracle E-Business Suite instance database is of type "RAC" and if you want to configure Parallel Concurrent Processing after the clone is completed, then it is recommended that you follow instructions described in the following My Oracle Support Knowledge Documents, depending on your RDBMS version:

• Document 312731.1, "Configuring Oracle Applications Release 11i with 10g RAC and 10g ASM"

• Document 757980.1, "Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i (11.1.0.6)"

• Document 455398.1, "Using Oracle Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i and Oracle Database 11g"

• Document 783188.1, "Certified RAC Scenarios for E-Business Suite Cloning" for more information on cloning of systems deployed on Oracle Real Application Clusters (RAC) is possible.

• Document 559518.1, "Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone" for information on cloning a Release 12 system on a RAC database

Preferences

The following properties are set in the Preferences page. Navigate to the Preferences page by navigating to Targets, then selecting Oracle E-Business Suite, then Preferences .

• Number of parallel threads/processes that will be used while zipping, transferring and unzipping the files under APPL_TOP directory of Apps Tier.

  • Minimum value: 1

  • Maximum value: 16

  • If the value is empty OR less than 1 OR greater than 16, then the default value of 8 is used.

• Number of parallel threads/processes that will be used while zipping, transferring and unzipping the files under Tools Oracle Home directory of Apps Tier.

  • Minimum value: 1

  • Maximum value: 8

  • If the value is empty OR less than 1 OR greater than 8, then the default value of 4 is used.

• Number of parallel threads/processes that will be used while zipping, transferring and unzipping the files under Tools Oracle Home directory of Apps Tier.

  • Minimum value: 1

  • Maximum value: 4

  • If the value is empty OR less than 1 OR greater than 4, then the default value of 2 is used.

• Number of parallel threads/processes that will be used while zipping, transferring and unzipping the files under COMMON_TOP directory of Apps Tier.

  • Minimum value: 1

  • Maximum value: 4

  • If the value is empty OR less than 1 OR greater than 16, then the default value of 2 is used.

Diagnostic Tests for Cloning

You should run diagnostic tests on your system in preparation for the cloning procedures to ensure your system is set up properly. These tests can be accessed from the Diagnostics dashboard, available from the Pack Diagnostics link on the Oracle Applications page. For more information on running diagnostic tests, see: Running Pack Diagnostics Tests.

The following tables list tests related to cloning.

PATH 
LD_LIBRARY_PATH 
LIBPATH 
SHLIB_PATH 
ORACLE_HOME 
ORACLE_SID 
PERL5LIB 
TNS_ADMIN 

s_base  
s_dbuser  
s_dbgroup   
s_appsuser   
s_appsgroup  
s_dbport  
s_port_pool 
s_config_home  
s_atName  
s_hostname  

s_base  
s_dbuser  
s_dbgroup   
s_appsuser   
s_appsgroup  
s_dbport  
s_port_pool 
s_hostname  

PATH 
LD_LIBRARY_PATH 
LIBPATH 
SHLIB_PATH 
ORACLE_HOME 
ORACLE_SID 
PERL5LIB 
TNS_ADMIN   

Running a Smart Clone Procedure

This section describes running a Smart Clone procedure. Smart Clone procedures can be used for both for Release 11i and Release 12.

At a high level, a Smart Clone procedure performs the following

1. Configures the target database

2. Clones and configures the applications tier from the source Oracle E-Business Suite system.

Steps 1 and 2 result in creating a target Oracle E-Business Suite system which is ready to use.

The following are prerequisites to running a Smart Clone procedure:

1. The target database must have already been cloned from the source Oracle E-Business Suite database.

   To do this, you can:

   • Use the Enterprise Manager 12c Database Plug-in to perform the required database cloning procedures OR

   • Use any other technology which suits your database cloning needs.

   Once the Target Database is cloned, discover it in Enterprise Manager 12c.

2. The Enterprise Manager user running the Smart Clone procedure must have the appropriate privileges.

   The following privilege setup instructions can be ignored if the user is a "Super Administrator".

   In order to execute the Smart Clone deployment procedure, a non-Super Administrator user must have certain target-level privileges and the resource privileges.

   The privileges listed below could be granted in many ways depending on the desired level of granularity of privileges to be granted to the user. For more details on granting privileges, please refer to the section "Configuring Security" in the manual Oracle Enterprise Manager Cloud Control Administrator's Guide 12c Release 1.

   The following outlines one of the ways of granting the required privileges for executing the Smart clone procedure.

   Target Privileges

   • Add any Target

     • Privileges applicable to all targets

       • Name: Add any Target (Description: Add any target in Enterprise Manager)

   • Operator any Target

     • Privileges applicable to all targets

       • Name: Operator any Target (Description - Ability to perform administrative operations on all managed targets)

       • Included Privileges - View any Target

       • Applicable Target Types - All Target Types

   Resource Privileges

   1. Job System resource:

      • Name - Job System

      • Description - Job is a schedulable unit of work that administrator defines to automate the commonly run tasks

      • Resource Type Privilege - Create

   2. Deployment Procedure:

      • Name - Deployment Procedure

      • Description - Deployment procedures are customizable orchestration routines for various Provisioning and Patching tasks

      • Resource Type Privilege - Create

3. The following Named Credentials must be defined:

   • Host target type

     • Authentication Target Type: "Host"

     • Credential Type: "Host Credentials"

   • Oracle E-Business Suite target type

     Please refer to the section Creating Named Credentials for Oracle E-Business Suite for instructions on creating the Oracle E-Business Suite Database Credentials.

To run a Smart Clone procedure

1. Navigate to the Cloning home page by selecting Targets menu > Oracle E-Business Suite. From the Oracle E-Business Suite launch page, select Cloning under Related Links.

2. Enter general information for the cloning process. This step captures information related to the target database already cloned and discovered in Enterprise Manager.

   Provide a transaction name for the Clone Name.

   Pick the Source Oracle E-Business Suite you would like to Clone from the LOV.

   Select the Target Database which is cloned from the Source Oracle E-Business Suite’s Database.

   Based on the type of Database (like Single Instance Database or RAC Database) rendering of this section will dynamically change. Currently following page snapshot shows the rendering of the section if it is a Single Instance Database.

   Provide the required details as shown in the Page Snapshot.

   You can click on Validate Database button or you can leave it to the Next button to perform the same action.

   

   If the target database is a RAC database, the Target Database Details is rendered differently, as shown in the following figure.

   

3. Enter RAC Target database details, if applicable.

   This step only applies if the target database is a RAC database. This step is skipped if the target database is of type Single Instance.

   If the Source Oracle E-Business Suite technology stack has the required patches applied for configuring customized names for listeners, then this page would automatically render in such a way that you provide your own name for the target database listeners by providing the required name for the field "New Listener Name".

   If the source Oracle E-Business Suite technology stack does not have the required patches, then Smart Clone will give default name to the listeners using the naming convention "LISTENER_<hostname>".

   If the Source Oracle E-Business Suite technology stack has the required patches applied for configuring the target database with "Scan Listeners", then the "Custom Scan Details" section is rendered with the "Scan Name" and "Scan Port" fields populated automatically. It is highly recommended not to change these values if it automatically populated. If for some reason the Scan Name and Scan Port fields are not populated (for example, if the cluster target instance discovered in Enterprise Manager has not populated these values yet as properties), then be sure to type in the correct values for these fields.

   Optionally, check the box "Use Custom Scan Name and Port" if you want to get the target database configured with the scan listener. If you do not check the box "Use Custom Scan Name and Port" then Smart Clone will clone the target database with virtual host names.

   If the Source Oracle E-Business Suite technology stack does not have the required patches then the "Custom Scan Details" section will not be rendered and the target database will be configured with virtual host names.

   If the target instance is already configured with scan listeners then by default the "Use custom scan name and port" box will be checked.

   

4. Enter source and target information.

   In this step, Smart Clone captures information related to the source and target.

   • All application tier information of the source Oracle E-Business Suite system is displayed.

   • You enter details for the target Oracle E-Business Suite system.

   For the case in which the source Oracle E-Business Suite system is deployed on a single applications tier, the Source/Target page is displayed as in the figure below.

   

   In the Available Target System Nodes region, choose the source host that can be used as a reference while cloning the target applications tier. Specify the target host from the LOV where Smart Clone should create the target applications tier.

   For the case in which the source Oracle E-Business Suite system is deployed on a multi-node applications tier, the Source/Target page is displayed as in the figure below.

   

   The "Source System Nodes" region shows the details of the source Oracle E-Business Suite applications tier in terms of

   • Number of nodes the applications tier is deployed on

   • Details of the services on the nodes.

   For the "Select Source Nodes for each service" region, In the case of a Release 11i multi-node applications tier system, you will need to choose the nodes for the services which are to be used as references for creating the Release 11i single node applications tiers.

   For Release 12, selecting the service in this section is unnecessary because the reference source host will be picked only from the "Available Target System Nodes" section.

   In the Available Target System Nodes region, choose the source host that can be used as a reference while cloning the target applications tier. Specify the target host from the LOV where Smart Clone should create the target applications tier.

   Note: Currently Smart Clone supports scaling down to a single-node applications tier only.

   For the target system node, click the Specify Details icon to update its properties.

5. The Target Node Summary page, navigable from the Specify Details icon is show in the following figure.

   

   The port pool and individual port values are updated from the source instance.

   If there is an invalid value in the port pool from the source instance: following error will be shown: "NOTE: Source Apps portpool context variable (s_port_pool) is invalid: <value>. Setting to default value '0'. Please update as needed!"

6. The next step is to Copy Parameters.

   

7. Enter Credentials.

   Smart Clone uses Named Credentials. You can select and test the named credentials on this page.

   Named credentials can be created by navigating to the Setup menu, then Security > Named Credentials, and clicking Create.

   

   Smart Clone requires the following credentials to be created:

   • Application Node OS Credentials and Database Node OS Credentials.

     • Authentication Target Type - Host

     • Credential Type - Host Credentials

   • Database Schema Credentials

     Please refer to the section Creating Named Credentials for Oracle E-Business Suitefor information on creating the Oracle E-Business Suite Database Credentials.

     Note: Database Schema credentials appear only when the source applications system is on Release 11iand using a non-shared file system.

   

   The Credentials page for a Smart Clone procedure where the source applications system is multi-node and the target database is non-RAC allows you to enter in and test all required credentials.

   

   The Credentials page for a Smart Clone procedure where the source applications system is single node and the target database is RAC allows you to enter in the required credentials.

   

8. Enter values for custom parameters.

   You can create directive steps to be integrated into a deployment procedure. For more information, see the Oracle Enterprise Manager Cloud Control Administrator's Guide.

   For a description on how to create a directive step and insert it into a procedure created using the "Create Like" feature and a shipped Smart Clone procedure, see:Adding Custom Steps to a Smart Clone Deployment Procedure.

   

9. Schedule the deployment.

   

10. Review your Smart Clone deployment procedure and click Finish.

    

Adding Custom Steps to a Smart Clone Deployment Procedure

This section describes creating custom steps and adding them to a Smart Clone deployment procedure. For more information generic information on how to create a Directive step and add it to a copy of an out-of-the-box Deployment procedure, refer to the Oracle Enterprise Manager Cloud Control Administrator's Guide.

Create a directive step

1. From the Enterprise menu, select Provisioning and Patching, then select Software Library.

   

2. Create a new directive. From the Actions menu, select Create Entity, then select Directives.

   

3. Specify a name and other attributes for the directive.

   

4. Add parameters for the directive.

   

5. Select the "Software Library" location and the script to be executed. In the example below, a Perl script is used.

   

6. Click Next and Save and Upload.

Create a copy of the out-of-box Smart Clone deployment procedure

1. From the Enterprise menu, select Provisioning and Patching, then select Procedure Library.

   

2. Select "Smart Clone" and click "Create Like".

3. Enter a name and other general information.

   

4. On the Procedure Steps tab, select the step before, inside, or after which you want to add the custom step, and click Insert.

   

5. Give the new step a name and enter additional information for the step.

   

6. Search for the directive and click Next.

   

7. Map the parameters as required in the Map Properties step.

   In our example, a text book will be provisioned in the Smart Clone procedure interview to provide the value for "Parameter 2".

   

8. Save the custom step and then save the procedure.

   

9. You can now submit the newly-created deployment procedure.

   

Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved.