Friday Dec 18, 2015

Platform Migration Certified for EBS 12.2 Application Tiers

We are pleased to announce that application tier migration for Oracle E-Business Suite Release 12.2 is now certified. You can now migrate an existing EBS 12.2 application (middle) tier server to any other Unix/Linux platform certified for EBS 12.2.  These platform migrations preserve patch levels, configurations, customizations, etc.

The E-Business Suite 12.2 application tier migration process requires EBS Release 12.2.3 or later updates to the 12.2 codeline. This documented process outlines only the process for an application tier migration:

What about application tier servers on the same platform?

For application tier migrations between systems of the same platform, you should follow the Rapid Clone process documented in this Note:

What about database tier platform migrations?

Database tier migration should be considered separately. For migration of the database tier, refer to the 'Database Migrations and Upgrades' section in this Note:

Related Articles

Monday Jul 16, 2012

Five Errors Customers Make When Cloning E-Business Suite 12 (Part 2)

This is the second in a series of articles about common technical myths or misunderstandings about the E-Business Suite. Other articles have covered installations, patching, migrations, upgrades, and maintenance. This article discusses cloning. Subsequent articles will cover patching, migrating, upgrading, and general maintenance.

Each article is absolutely not definitive and I’d be interested in comments from readers who think there are other misconceptions about the day-to-day maintenance and upgrade of a typical E-Business Suite environment.

: Assuming that use of the Rapid Clone utility is optional when cloning your Apps environment.

ORACLE’S RECOMMENDATION: Rapid Clone greatly simplifies the process of cloning your E-Business Suite environment. Simply copying your E-Business Suite environment to new host machines, editing the context files to reflect the new environment and then running AutoConfig is not a supported cloning method. Devising your own cloning methodology that bypasses Rapid Clone is a dangerous strategy. If Rapid Clone does not work for you, then raise a Service Request and ask for help in fixing the issue. Do not create an alternative cloning method that you hope will sidestep whatever issue you are seeing.

: Assuming that the preclone scripts only need to be run once on an environment.

ORACLE’S RECOMMENDATION: You must run the preclone scripts immediately before each clone, prior to shutting down the application and database tiers in order to copy the files for cloning (or RMAN backup). It’s also good practice to remove or rename the database tier $ORACLE_HOME/appsutil/clone and application tier $COMMON_TOP/clone before running the preclone script. Always check the cloning documentation for the latest patches before each clone.

: Mistakenly using Rapid Clone to migrate from 32 bit Linux to 64 bit Linux.

ORACLE’S RECOMMENDATION: Although these platforms are binary compatible, cloning your E-Business Suite from 32 bit Linux to 64 bit Linux will only produce a 32 bit E-Business Suite environment on your 64 bit operating system. In order to fully exploit your 64 bit operating system you should follow specific migration documentation for your E-Business Suite environment. The same applies to other certified operating systems available as both 32 and 64 bit.

:  Mistakingly forgetting to update the central inventory when overwriting a previous clone with a new clone in the same location.

ORACLE’S RECOMMENDATION: If you regularly repeat a clone to the same location on a target node, you must ensure the central inventory entries for the previous clone are removed before configuring the new clone. As with a repeated installation, when deleting an E-Business Suite environment prior to cloning to the same location, in addition to shutting down and deleting files, you must also remove its entries from the central inventory. The central inventory is a file based repository of all Oracle homes installed on a node. This central inventory may exist outside the E-Business Suite file system and is not always removed when you remove the E-Business Suite file system. If the central inventory contains entries for previously deleted E-Business Suite environments then subsequent new clones may fail.

COMMON ERROR #5: Assuming that the clone is not a completely accurate copy.

ORACLE’S RECOMMENDATION: A system created using Rapid Clone is the most genuine and supported copy you can create. It has an identical database, application tier and technology stack as the source environment it was created from. The only significant difference between a source and target clone environment is the data specific to the new hardware (node names, directory locations etc.). It is supported to clone your production environment, apply patches to the clone and then clone the patched system back to become your new production environment. Assuming the cloning documentation is followed correctly, an E-Business Suite environment does not degrade through being repeatedly cloned.


Related Articles

Thursday Sep 02, 2010

Updated Platform Migration Procedures Certified for EBS 12

We are pleased to announce the certification of the Platform Migration Methodology for Oracle E-Business Suite Release 12.  The existing documentation has been updated to be generic for all Release 12 versions.

The platform migration process provides a way to quickly and easily move an existing Oracle E-Business Suite application tier to a different platform, allowing you to utilize different hardware for the application tier.

The migration utility retains the exact Oracle E-Business Suite patch level, so that no APPL_TOP or database synchronization is necessary.  This also allows you to retain many customizations.

The existing procedure available for 12.0 has been optimized and modified for all Release 12.x versions. You can find more details in the following document available in My Oracle Support:
Some additional considerations
  • This migration methodology requires at least E-Business Suite version 12.0.4 for Release 12.0 and 12.1.1 (or higher) for Release 12.1.
  • This methodology applies to the Application Tier (middle tier) only.  The database tier is not covered by this process.
  • Migration to Windows-based target servers is not supported at this time
  • The platform migration procedure is not supported with Linux running on IBM System z (Source or Target) at this time.
Your feedback is welcome

We're extremely interested in hearing about your use cases and your experiences with these updated procedures. Please post a comment here or drop us a line with your thoughts.

Related Articles

Monday Dec 07, 2009

Oracle E-Business Suite Install and Cloning Best Practices (OpenWorld 2009 Recap)

Experienced E-Business Suite systems administrators know that there never seem to be enough EBS testbeds for everyone.  It doesn't take long for an Apps sysadmin to realize that having a solid understanding of the various options for building and cloning EBS environments is an essential part of his or her toolkit.  

Flow diagram showing adpreclone process and what it does on the EBS database tier
If you've been wondering about the different options for building EBS environments, look no further.  Max Arderius is a member of our Applications Technology Group.  His OpenWorld session covered the E-Business Suite's Rapid Install and cloning techniques in detail:
Max drilled into the following topics in his presentation:
  • Installing the E-Business Suite
    • Rapid Install overview
    • Standard vs. Express Install
    • Filesystem implications of upgrading and existing system
    • Upgrade considerations
    • Installation of the latest Applications technology stack
  • Cloning techniques
    • Overview of cloning tools: Rapid Clone vs Application Management Pack
    • Details of Rapid Clone process
      • What does on the database and applications tiers
      • What happens during the cloning process
      • What does on the database and applications tiers
      • Comparison of command line options
      • configuration command
    • Application Management Pack cloning process
      • Comparison of Application Management Pack cloning options
      • Source-to-image, image-to-target cloning
      • Hot cloning
      • Real Application Clusters (RAC) cloning
      • Data scrambling during the cloning process
    • Custom cloning techniques
      • Source-to-target direct synchronization
      • Cloning using rsync
      • Maximum Availability techniques using Oracle DataGuard and rsync to a standby database
      • OracleVM cloning using functional technical VM templates
  • Best practices
    • Pointers to useful resources
    • Comparison of using media vs. staged images
    • Remote installation best practices and considerations
    • Fully qualified hosts and file permissions
    • Resource limits and kernal parameters
    • Temp directories and swap spaces
    • Techstack registration
    • Global inventory and multiple inventories
Listening to the Session

If you registered for OpenWorld, here's a link to the OpenWorld On Demand page where you can download the presentation or listen to the live recording of this session.

Related Articles

Tuesday Jun 02, 2009

Applications Change Management Pack 3.0 and Applications Management Pack 3.0 Now Available

Our E-Business Suite Applications Technology Group recently released a new product, the Application Change Management Pack (ACMP), and a new version of their Application Management Pack (AMP).

The Application Change Management Pack is noteworthy because it provides three new tools for automating updates to multiple E-Business Suite instances:

  • Customization Manager automates the packaging of your customizations into AD-compliant packages that can be deployed across multiple E-Business Suite instances.  Before packaging, the Customization Manager validates your customizations against Oracle's software coding best practices.

    Screenshot of Application Change Management Pack showing package creation step

  • Patch Manager integrates with Oracle Metalink and automatically downloads and deploys different types of patches across multiple (single or multi-node) E-Business Suite instances.

    Screenshot of patch wizard acmp plug-in screen

  • Setup Manager helps manage functional setups that need to be duplicated across multiple E-Business Suite instances.

    Screenshot of ACMP Setup Manager screen

We've profiled the Application Management Pack in previous articles.  Application Management Pack extends Enterprise Manager Grid Control to monitor and managed E-Business Suite components.  Notable new features in Version 3.0 are:

  • Advanced Discovery: allows you to monitor and manage E-Business Suite systems running advanced topologies such as Real Application Clusters (RAC)
  • EBS Administration:  provides a user interface to start or stop E-Business Suite components individually or the E-Business Suite as a whole
  • Hot cloning for Oracle E-Business Suite Release 12:  Automates cloning of an Oracle E-Business Suite Release 12 system in hot mode, without shutting down the database. 
  • RAC cloning for Oracle E-Business Suite Release 12:  Enables cloning of Oracle E-Business Suite Release 12 databases running Real Application Clusters to another RAC or single-node (non-RAC) environment.


  • Linux x86 (32-bit)
  • Enterprise Manager Grid Control 10g Release 4 (10gR4)
  • Oracle E-Business Suite Release 11.5.10.CU2 or
    Oracle E-Business Suite Release 12.0.4 or higher

Certifications for other operating system platforms, Enterprise Manager Grid Control release 10g Release 5, and other E-Business Suite releases are underway.  You're welcome to monitor or subscribe to this blog for updates for these certifications, which I'll post as soon as soon as they're available.


Both Application Management Pack for Oracle E-Business Suite and Application Change Management Pack for Oracle E-Business Suite are separately licensed products. Application Management Pack for Oracle E-Business Suite Version 3.0 is a mandatory prerequisite for Application Change Management Pack for Oracle E-Business Suite Version 3.0 and should be licenced separately.


The Application Management Pack and Application Change Management Pack are available as a single install using Oracle Universal Installer.  They can be downloaded via:


Related Articles

Monday Apr 20, 2009

New Whitepaper: Manually Cloning Apps 11i Databases Running 10g or 11g RAC

Our Applications Technology Group recently published a matrix showing certified cloning scenarios for E-Business Suite databases running in Real Application Cluster (RAC) configurations.  Since then, some concerns have been raised about the lack of Rapid Clone support for EBS environments running on the 10g and 11g databases.

In response to those concerns, our Applications Technology Group has published a new whitepaper:

This new whitepaper describes a certified and supported method for manually cloning Apps 11i environments running 10g or 11g RAC.  The Note assumes a high degree of familiarity with Oracle Applications AD Utilities, RapidClone, AutoConfig, Recovery Manager, and SQL*Plus.

Related Articles

Wednesday Oct 29, 2008

EBS 12: Install + Cloning Techniques Deep Dive (OpenWorld 2008 Recap)

I'm highlighting OpenWorld 2008 presentations that cover some of the most popular E-Business Suite technology stack topics. A catalog of all of the Applications Technology track sessions with links to the presentations is available here:

If you're looking for a good overview of how Oracle E-Business Suite Release 12 environments can be cloned, you should check out the following presentation from Max Arderius, Development Manager in the Applications Technology Group, and Biju Mohan, Product Manager in the Applications Technology Group:

Graphic showing differences between Rapid Clone and automated cloning via Applications Management Pack AMP

[Read More]

Friday Aug 08, 2008

Rapid Clone Updates for July 2008 Available for Apps 11i and 12


The Rapid Clone updates for Release 11i and 12 are released simultaneously twice a year in January and in July. The latest updates to both versions are now available in the following downloads:


These patches include more than 91 and 67 Bug fixes for 11i and R12 respectively. The corresponding Rapid Clone Metalink Notes have been updated accordingly.

The July 2008 updates fix more than 91 cloning-related issues for Release 11i and more than 67 for Release 12; see the respective READMEs for the list of bugs fixed.

  • Note 230672.1 : Cloning Oracle Applications Release 11i with Rapid Clone
  • Note 406982.1 : Cloning Oracle Applications Release 12 with Rapid Clone
Related Articles

Thursday Feb 28, 2008

Scrambling Sensitive E-Business Suite Data During Cloning

Enterprise Manager 10g Grid Control allows you to manage all of your Oracle E-Business Suite systems from a single console.  The Application Management Pack (AMP) for Oracle E-Business Suite, Release 2.0.0 and 2.0.1 extends EM 10g Grid Control to manage Oracle Applications systems.


One of the key features of the Applications Management Pack is the ability to clone an Oracle E-Business Suite system automatically.  While cloning environments, administrators can modify the standard cloning process to include some custom actions. One such custom action is data

Data scrambling is the process of obfuscating or removing sensitive data, and can be used by functional administrators and database administrators when cloning an environment that contains sensitive information.

Data Scrambling Characteristics

The key characteristics of Data Scrambling are:

  • The scrambling process is irreversible, so that the original data cannot be derived from the scrambled data.
  • The scrambling process is repeatable (with the same parameters) and can be used for multiple cloning processes.

Key Data Scrambling Terms

Attribute:  Group of columns in one or more tables representing a single, logical E-Business Suite-wide value such as customer name

Tables to Purge:   Tables selected to be purged for rows matching user-defined criteria. This table selection allows the removal of sensitive data such as transaction histories before allowing applications to access to the system.

Policy:  Functional groupings of Attributes and Tables to Purge related to one or more applications in the E-Business Suite. For example: "GL Policy" or "AR Policy".

Policy Set:  Policy sets are groups of policies. Multiple policy sets can contain overlapping policies.  Example: "Financial Policy Set"

Configuring Data Scrambling1: Flow diagram showing data scrambling policy definition process

Preparing for Data Scrambling

  1. Data scrambling is configured through the Oracle Applications Manager.  To enable data scrambling, set the site-level profile option OAM: Data Scrambling Enabled to "Yes".
  2. Functional administrators define the attributes and map them to database columns.
  3. Functional administrators collect attributes together to define policies and policy sets.

Scrambling the Data

The configuration defined in Oracle Applications Manager for data scrambling can be utilized within the Apps Management Pack during the cloning process.

The Database Administrator specifies the policy sets to scramble the source data, initiates and then monitors the data scrambling process.

The source data from the original instance is sent through the data scrambling engine, which then scrambles the data.

Configuring Data Scrambling2:


Related Articles

Monday Feb 04, 2008

RapidClone Updates Available for Apps 11i and 12

Our ever-handy RapidClone utility allows you to create a standalone copy of an existing Oracle Applications system. There are many scenarios where it's useful to clone an Applications environment, including:

  • Standard cloning - Making a copy of an existing Oracle Applications system, for example a copy of a production system to test updates.
  • System scale-up - Adding new machines to a system to provide the capacity for processing an increased workload.
  • System transformations - Altering system data or file systems, including actions such as platform migration, data scrambling, and provisioning of high availability architectures.
  • Patching and upgrading - Delivering new versions of Applications components, and providing a mechanism for creating rolling environments to minimize downtime.
Latest RapidClone Consolidated Fixes Available for Download

The latest updates to both the Release 11i and 12 versions of RapidClone are now available in the following downloads:
The January 2008 updates fix 36 cloning-related issues for Release 11i and 57 cloning-related issues for Release 12; see the respective READMEs for the list of bugs fixed.

Related Articles

Wednesday Aug 01, 2007

R12 Rapid Clone on Windows Now Available

Cloning is the process used to create a copy of an existing Oracle Applications system.  If you're running Release 12 on Microsoft Windows Server 2003 (32-bit), you can now clone your environments with Rapid Clone. 

Windows Server 2003 Logo: Microsoft Windows Server 2003 logo
Until today -- prior to the combined availability of these two patchsets -- Windows users have been restricted from using Rapid Clone.  If you had attempted to clone a Windows-based R12 environment without these prerequisites, you would have encountered issues with executing a few scripts, and some registry entries would have been set incorrectly for a number of services.

For full details about cloning Release 12 environments, see:

Wednesday Apr 04, 2007

Fully Automated Cloning for Release 11i and 12

Cloning is the process of creating an identical copy of an already existing Oracle Applications system.  Cloning is a regular part of an Apps DBA's responsibilities, so you're probably already familiar with the latest Rapid Clone utility and its predecessor,, the original AD Clone Utility.  If you've used those tools in the past, you likely also know that overall cloning process requires some user intervention for things like the APPS password and so on. 

Enterprise Manager Screenshot:

A customer recently asked whether the following cloning process can be fully automated, so that no user intervention is required at all:
  1. Shut down the PROD environment for both the application server and database tier
  2. Do an offline preclone of both tiers
  3. Copy both tiers to another server (the sandbox environment)
  4. Restart the PROD environment
  5. Do an offline postclone of both tiers for the sandbox environment
  6. Start the sandbox environment
In researching that, I was pleased to learn that this kind of automation is a new feature in the latest Application Management Pack for Oracle E-Business Suite for Enterprise Manager Grid Control 10gR3. 

The management pack automates the cloning of both Release 11i (11.5.10 with ATG RUP4) as well as Release 12 environments.  You go through a step-by-step interview process to configure the clone routine once, and then you can reuse the cloning routine as many times as you wish.  In addition, the cloning routing can send out a notification if it failed.

Very slick.  If you've had a chance to try this, I'd be interested in hearing about your experiences with this new feature.


Wednesday Aug 30, 2006

Cloning Discoverer End-User Layers

Given its utility, I'm highlighting a recent blog comment from Steve Fitzgerald, one of our Oracle BI specialists.  This was in response to our In-Depth: Cloning OracleAS 10g + E-Business Suite Environments article.

Discoverer Export Wizard Screenshot:

For the Discoverer users of the E-Business Suite, I will point your readers to "some old-fashioned elbow grease" to fill in the gaps. This will apply to
import/export of an End-User Layer (EUL) at the database level.  It may not be necessary when cloning the entire database and not modifying the EUL, but will be if creating a DEV/TEST/PROD type clone. It might save a headache or two down the line :-).

Discoverer recognizes EULs using unique reference numbers.  However, if you use the database export and import utilities to copy an EUL, the new EUL (including its reference number) will be identical to the original EUL.  When EULs have the same reference number, EUL consistency issues can arise if you do both of the following:
  • If you modify objects in both the original EUL and in the new EUL

  • Having modified objects in both EULs, if you then attempt to copy objects between the two EULs using the Discoverer Export Wizard and Import Wizard (or the Discoverer /export and /import commands)
To avoid potential EUL consistency
issues, run the eul5_id.sql script as the owner of the new EUL.  The eul5_id.sql script gives a new refererence number to the new EUL and thereby avoids any potential EUL consistency issues.



« August 2016