Cloning an On-Premises Oracle E-Business Suite Solaris on SPARC Environment to Oracle Cloud

 


Options



Before You Begin

Purpose

This tutorial provides instructions for backing up and migrating your on-premises Oracle E-Business Suite Solaris on SPARC Model 300 (part of the Oracle Compute Cloud Service - Dedicated Compute Capacity in Oracle Cloud). Both your application and database tiers will be restored to the Oracle Compute Cloud Service.

In this tutorial, you will:

  • Execute a script to package, back up, and move the on-premises Oracle E-Business Suite installation to a pre-provisioned domain.
  • Configure Oracle E-Business Suite for use in Oracle Compute Cloud Service.

Background

SPARC Model 300 is a secure, reliable, low-cost, standards-based infrastructure service. You can use it to rapidly access domains on Oracle Cloud with all the necessary storage and networking resources to support Oracle E-Business Suite. The SPARC Model 300 service includes the following:

SPARC Compute

  • 300 OCPUs (300 SPARC M7 Cores)
  • Each Customer Domain (DomU) has 30 OCPUs, 600 GB virtual system boot disk, and 442 GB of memory available for customer workloads
  • Customer Domain (DomU)
    • Solaris 11.3 pre-installed and configured by Oracle
    • Managed and maintained by customer. OPC has no access to Customer Domain.
      • Oracle not responsible for maintaining and updating OS versions or network interface firmware.
    • Virtualization technology support
      • Oracle Solaris Zones are supported
        • Oracle Solaris 11 Non-Global Zone, Kernel Zone, and Oracle Solaris 10 Branded Zones
        • Oracle Solaris 8 and 9 are NOT supported
        • Standard Oracle Solaris version support applied including SRU support
    • No LDOM creation/configuration support
    • Customer Domain rebuild requires SR to be filed with OPC
      • Customer cannot rebuild domain themselves

Integrated ZFS Storage

  • 60 TB of usable capacity on integrated ZFS Storage Appliance for Virtual Machines and application or database storage

For more information on this service, see the SPARC Model 300 website.

What Do You Need?

To perform the steps in this tutorial, you need:

  • Applications database administrator (Apps DBA) skills.
  • An understanding of the relevant information in My Oracle Support Knowledge Document 2066260.1, Getting Started with Oracle E-Business Suite on Oracle Cloud.
  • A working knowledge of Oracle Compute Cloud Service features and terminology, as described on the SPARC Model 300 website.
  • The following operating system utilities installed and available on the source and target systems:
    • gnu-tar
    • gzip
    • OpenSSL
    • SunSSH, including the ssh-keygen utility
  • A subscription to SPARC Model 300. You must contact an Oracle Sales representative to purchase a subscription. You can also access pricing and other product information on the Compute Service website. In order to process and complete a subscription, administrative and network information (such as reserved IP subnets, SSH keys) will need to be provided.
  • A secure VPN connection set up between your data center and the Oracle SPARC Model 300 Service. Submit a service request (SR) to set this up.
  • To meet the following certified release requirements listed in the table below:
    Certified Oracle E-Business Suite and Database Releases for Source System Target Application/Database Tier Location

    Oracle E-Business Suite Release 12.2 (Release 12.2.3 or a later update) on Oracle Solaris on SPARC with database and middle tier patches recommended by the EBS Technology Codelevel Checker (ETCC) and an AD-TXK codelevel of Delta 8 or higher (see Footnote 1), with either:

    • Oracle Database Release 11.2.0.4
    • Oracle Database Release 12.1.0.2
    SPARC Model 300

    Oracle E-Business Suite Release 12.1.3 on Oracle Solaris on SPARC with the specified prerequisites (see Footnote 2), with either:

    • Oracle Database Release 11.2.0.4
    • Oracle Database Release 12.1.0.2

    Footnote 1: For more information, refer to My Oracle Support Knowledge Document 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 and Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes.

    Footnote 2: For AD, AutoConfig template, and Rapid Clone patch prerequisites and other information, see My Oracle Support Knowledge Document 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone.

    Notes:

    • The target SPARC Model 300 system, based on SPARC M7 processors, has specific minimum Java version requirements. Refer to the appropriate Installation and Upgrade Notes mentioned below for upgrading Java on your source system:
      • Document 761568.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Oracle Solaris on SPARC (64-bit)
      • Document 1330702.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Oracle Solaris on SPARC (64-bit)
    • The source system can be either an Oracle Real Application Clusters (Oracle RAC) system or a single-node database

Process Overview

To move your Oracle E-Business Suite installation from the source system to the Oracle Compute Cloud Service and configure the domain, you must complete the following tasks:

  1. Log in to the Oracle Compute Cloud Service through your VPN client.
  2. Download the Oracle E-Business Suite Clone Utility for Oracle SPARC Cloud.
  3. Prepare the source system for Oracle E-Business Suite cloning.
  4. Run the EBS Cloud backup utility.

Logging in to the Oracle Compute Cloud Service Through VPN

  1. Enter the following command:
    $ ssh -i /path/to/private_key opc@<public_ip_address_of_domain>
  2. When prompted, enter the passphase you provided for your SSH key pair.

After you log in to the service, you can begin to deploy your virtual environment by creating users, zones, storage volumes, and modify your network configurations as needed. You should also refer to the server product notes and the corresponding installation and upgrade notes for your particular Oracle E-Business Suite release for other operating system requirements (such as operating system packages and patches) that may be required.

Downloading the Oracle E-Business Suite Cloning Utility to the Source Oracle E-Business Suite Environment

  1. Download Patch 25822183 from My Oracle Support.
  2. Extract the downloaded patch using the following command in a directory with at least 300 MB of free space.
    $ cd <download folder>
    $ unzip p25822183_R12_SOLARIS64.zip
  3. Change the permission to "execute" for all the downloaded scripts.
    $ cd <extracted folder>
    $ chmod +x *.pl
    $ chmod +x lib/*.sh        

Preparing the Source System for Oracle E-Business Suite Cloning

The following steps prepare the source system in order to enable cloning of the Oracle E-Business Suite installation to the Oracle Compute Cloud Service domain.

  1. Add the IP address of the cloud domain in the /etc/hosts file of the source Oracle E-Business Suite system.
  2. Ensure that SSH connectivity between all participating hosts is configured as shown in the image below, either with or without a passphrase. Participating hosts include host in which the remote clone utility is executed, source Oracle E-Business Suite host(s), and Oracle Cloud host(s).

    You must copy the public key from host 1 to ~/.ssh/authorized_keys file of host 2, as described in the following table:
      Host 1 Host 2
    1 Host in which the remote clone utility is executed Source database tier host
    2 Host in which the remote clone utility is executed Source primary application tier host
    3 Source database tier host Target database tier host
    4 Source primary application tier host Target application tier host
    Note: Sometimes, your login to Oracle Cloud may fail with: "WARNING: Your password has expired." If this happens, reset the password of the user on the Oracle Cloud host.
  3. In the extracted folder, update the cln.props file as follows:

    Property Description Applicable Release(s)
    1 MODE Execution mode. This parameter must be either commented out or, if your source database is a RAC database, it should be set to RAC-to-nonRAC. 12.2/12.1
    2 BACKUP_TYPE Ensure that this is commented out. 12.2/12.1
    3 HOST.SRC.DB Full hostname (including domain) of source database system 12.2/12.1
    4 OS_USER.SRC.DB Operating system username to connect using SSH to source database server 12.2/12.1
    5 OS_PASSWORD.SRC.DB Operating system password to connect using SSH to source database server 12.2/12.1
    6 STG_DIR.SRC.DB Directory that temporarily stores database zip files 12.2/12.1
    7 HOST.SRC.APPS Full hostname (including domain) of source applications system 12.2/12.1
    8 OS_USER.SRC.APPS Operating system username to connect using SSH to source application tier server 12.2/12.1
    9 OS_PASSWORD.SRC.APPS Operating system password to connect using SSH to source application tier server 12.2/12.1
    10 STG_DIR.SRC.APPS Directory that temporarily stores application tier zip files 12.2/12.1
    11 CONTEXT_FILE.DB.SRC Source database system complete context file path 12.2/12.1
    12 CONTEXT_FILE.APPS.SRC Source application system complete context file path 12.2/12.1
    13 APPS_PASS Oracle E-Business Suite Apps schema password 12.2/12.1
    14 HOST.TGT.DB Full hostname (including domain) of target database server. 12.2/12.1
    15 OS_USER.TGT.DB Operating system username to connect using SSH to target database server 12.2/12.1
    16 OS_PASSPHRASE.TGT.DB Passphrase with which the SSH key is generated to authenticate between the hosts 12.2/12.1
    17 STG_DIR.TGT.DB Directory that temporarily stores database zip files on the target database server 12.2/12.1
    18 HOST.TGT.APPS Full hostname (including domain) of target application tier server. 12.2/12.1
    19 OS_USER.TGT.APPS Operating system username to connect using SSH to the target applications server 12.2/12.1
    20 OS_PASSPHRASE.TGT.APPS Passphrase with which the SSH key is generated to authenticate between the hosts 12.2/12.1
    21 STG_DIR.TGT.APPS Directory that temporarily stores application tier zip files 12.2/12.1
    22 DB_SID.TGT Target database Oracle SID 12.2/12.1
    23 DB_BASE_DIR.TGT Target database system base directory 12.2/12.1
    24 APPS_BASE_DIR.TGT Target application system base directory 12.2/12.1
    25 APPS_INST_BASE_DIR.TGT Target application system domain base directory 12.2/12.1
    26 DB_PP.TGT Database tier port pool on the target system 12.2/12.1
    27 THREAD_POOL_SIZE Configurable parameter to specify number of threads used by the utility for intrinsic operations such as remote transfer or extractions of compressed files. 12.2./12.1
    28 THREAD_POOL_SIZE.TRANSFER Additional configurable parameter that is used to specify number of threads for remote transfer operation and is commented out by default.
    Note: When MODE is set to RAC-to-nonRAC, this parameter is required and should be uncommented.
    12.2/12.1
    29 WLS_ADMIN_PASS WebLogic Admin server password 12.2
    30 APPS_RUN_PP.TGT Application tier run file system port pool on the target server 12.2
    31 APPS_PATCH_PP.TGT Application tier patch file system port pool on the target server 12.2
    32 APPS_121_PP.TGT Application tier port pool on target server 12.1
    33 HOST.STAGE Ensure that this is commented out. 12.2/12.1
    34 OS_USER.STAGE Ensure that this is commented out. 12.2/12.1
    35 OS_PASSWORD.STAGE Ensure that this is commented out. 12.2/12.1
    36 STG_DIR.STAGE Ensure that this is commented out. 12.2/12.1
    37 PROXY_PROTOCOL.SRC.DB Proxy server protocol used by SSH for communication with cloud domains. 12.2/12.1
    38 PROXY_PORT.SRC.DB Proxy server port. 12.2/12.1
    39 PROXY_USER.SRC.DB Proxy server username. 12.2/12.1
    40 PROXY_PASSWORD.SRC.DB Proxy server password. 12.2/12.1
    41 CUSTOM_PRIVATE_KEY_LOC.SRC.DB Full path to private key used for SSH communication with cloud domains. 12.2/12.1

    Notes:

    • The stage directories (STG_DIR) must have enough free space. For example, if the source Oracle E-Business Suite database data directory size is around 200 GB, then the stage directories must have at least 50 GB of free space.
    • The target Oracle E-Business Suite hosts must have enough space for the stage directory as well as the Oracle E-Business Suite file system.
    • The passwords provided in the cln.props file will be encrypted after the first run. If you subsequently change any of the passwords, you must follow the steps below to ensure that the cln.props file has the updated passwords in the correct format.
      1. Open the cln.props file in a text editor such as vi and edit the password that needs to be changed.
      2. Run a command such as the following to encrypt the newly updated password. For example, if you want to change the password for OS_PASSWORD.SRC.APPS in the cln.props file:
        $ export UTILITY_DIR=
        $ UTILITY_DIR/RemoteClone_v1.6/3pt/jre/bin/java -cp $UTILITY_DIR/RemoteClone_v1.6/lib/cln_utils.jar \
        oracle.apps.ad.remoteop.cloneutil.OPCCloneUtil -encryptPassword -clnPropsFile \
        $UTILITY_DIR/RemoteClone_v1.6/cln.props -property OS_PASSWORD.SRC.APPS -passwordKeyFile \
        $UTILITY_DIR/RemoteClone_v1.6/conf/password.key  
    • If you subsequently make any further changes to a password in this file, you must encrypt the new password by running a command such as the one given above. If you do not, the tool will fail to obtain the correct password.
  4. Increase the following timeout values in the Applications context file (without re-running AutoConfig):
    • For Release 12.1.3:
      <timeout oa_var="s_opmntimeout" osd="unix">12000</timeout>
      <timeout oa_var="s_apctimeout">12000</timeout>
      <timeout oa_var="s_oacoretimeout">12000</timeout>
    • For Release 12.2.x (Run Edition):
      <timeout oa_var="s_nodemanagertimeout" osd="unix">12000</timeout>
      <timeout oa_var="s_adminservertimeout" osd="unix">12000</timeout>
      <timeout oa_var="s_opmntimeout" osd="unix">12000</timeout>
      <timeout oa_var="s_apctimeout">12000</timeout>
      <timeout oa_var="s_oacoretimeout">12000</timeout>
  5. Customers whose source database is an Oracle RAC database should ensure that valid archive logs are located in a shared storage area. Archive logs that have been relocated or removed should be marked as expired in catalog. References in the catalog should be deleted.
    The following commands can be used to check and remove expired archive logs:
    RMAN> CROSSCHECK ARCHIVELOG ALL;
    RMAN> DELETE EXPIRED ARCHIVELOG ALL;
  6. Update the SSH configuration parameters on the Oracle Compute Cloud Service domain using the following instructions:
    1. Update the /etc/ssh/sshd_config file.
      1. Make a backup copy of the /etc/ssh/sshd_config file.
        $ cp /etc/ssh/sshd_config  /etc/ssh/sshd_config.ORIG
      2. Using a text editor such as vi, open the /etc/ssh/sshd_config file for editing.
      3. In the /etc/ssh/sshd_config file, add the following lines to allow multi-threaded transfer of files and to prevent client timeout:
        # To allow multi-threaded transfer of files.  
        MaxStartups 100  
        # To prevent client timeout.   
        ClientAliveInterval 100  
        ClientAliveCountMax 99999
      4. Also in the /etc/ssh/sshd_configfile, add lines to specify the user that you want to clone to the "AllowUsers" list. For example, if you intended to create the target Oracle E-Business Suite on the Oracle Compute Cloud Service domain as user oracle, make the following addition:
        # Specify user for target Oracle E-Business Suite domain.  
        AllowUsers opc oracle
      5. Save the updated /etc/ssh/sshd_config file and exit the editor.
    2. Stop and restart the sshd daemon.
      $ svcadm disable network/ssh (to stop)
      $ svcadm enable network/ssh (to start)
    3. As part of submitting your subscription, you should have already provided an SSH public key which will have been copied into the authorized keys file for every domain (DomU) on the Oracle Compute Cloud Service. If this has not been set up, then use the following steps to update the keys file:
      1. Copy the content of the public key file generated on the source system, as mentioned in the previous screen (default location: ~/.ssh/id_rsa.pub).
      2. Log in to the Oracle Cloud host as the oracle user, and paste the content from the previous step to the ~/.ssh/authorized_keys file of the user account that will be used to clone Oracle E-Business Suite.
      3. If you have a separate application tier, perform step ii again, but this time for the applmgr account.

Your Oracle Compute Cloud Service domain is now ready for your on-premises Oracle E-Business Suite installation to be cloned to it.

Running the EBS Cloud Clone Utility

The following is a high-level summary of the steps performed in this section:

  1. Package the on-premises Oracle E-Business Suite installation.
  2. Move the installation bits on to the cloud domain provisioned above.
  3. Configure Oracle E-Business Suite for end-user access.

Note: Please review the "Known Issues" section in the Installation and Upgrade Notes for your Oracle E-Business Suite release for other system configuration issues that may apply:

  • Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Oracle Solaris on SPARC (64-bit) (My Oracle Support Knowledge Document 761568.1)
  • Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Oracle Solaris on SPARC (64-bit) (My Oracle Support Knowledge Document 1330702.1)

Note: For Oracle E-Business Suite Release 12.1 customers, you must set the PERL5LIB environment variable on the source system BEFORE running this utility and on the target system AFTER the utility has completed successfully.

Refer to "Appendix B: Setting the PERL5LIB environment variable on the Database tier" in My Oracle Support Knowledge Document 387859.1, Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12, for instructions on how to set the PERL5LIB environment variable.

To perform the steps:

$ cd <extracted directory>
$ perl ./ebsclone.pl

Configuring the Oracle E-Business Suite Domain

Configuration of the Oracle E-Business Suite database and application tiers is conducted automatically during the cloning from the source instance to the cloud domain. The clone script configures the database tier file system and then the application tier. The time taken for the configuration will depend on the network speed and the shape of the domain. You should allow at least several hours. Do not attempt to use the new Oracle E-Business Suite environment until the configuration is reported as complete.

Want to Learn More?

Change Log

Date Description
2019-04-24
  • Updated footer.
2018-06-29
  • Minor formatting enhancements.

2017-06-20

  • Updated description of properties in cln.props table in "Preparing the Source System for Oracle E-Business Suite Cloning" section.
  • Initial publication.