Migrating E-Business Suite Application Tier Servers to Linux

If your E-Business Suite environment is hitting the ceiling for performance, you should first tune and optimize it to squeeze the most of your existing hardware.  At some point, you may decide to scale up your application tier with multiple nodes behind a load-balancer.  As part of that process, you might begin considering replacing large SMP servers on your application tier with a pool of servers running Linux on commodity hardware. 

Indeed, this is the architecture that we use to run Oracle's own global E-Business Suite Release 12 implementation.  We have four large Sun database servers fronted by almost 40 application tier servers running Oracle Enterprise Linux (OEL):

gsi_Architecture_Diagram_R12.png

If you're considering a move to Linux for your Apps middle tier servers, you will find the following two Notes invaluable:
You can use these Notes to migrate an Oracle application (middle) tier to any platform that is supported with the Rapid Installs for both Oracle E-Business Suite Release 11i and 12.

The processes described in those Notes provides a certified way to quickly and easily move an existing Oracle application tier system to a different platform, allowing you to utilize different hardware for the Oracle application tier. The migration utility retains the exact Oracle E-Business Suite patch level so that no APPL_TOP/Database synchronization is necessary; this also allows you to retain many customizations.

Related Articles

Comments:

Hi Steven,

How about migrating database tier? Any notes/steps to be followed? Is it enough just by doing export/import and then proceed with apps tier?

Posted by Anuar on February 02, 2010 at 02:05 PM PST #

Hi, Anuar,

Yes, the database tier is very straightforward. The export/import Notes for the respective database releases are sufficient for that tier's migration between platforms.

Regards,
Steven

Posted by Steven Chan on February 04, 2010 at 03:22 AM PST #

The R12 note only seems to reference 12.0.x, is this also supported under 12.1.x?

Posted by Ian Neal on February 04, 2010 at 08:02 AM PST #

Hello, Ian,

Yes, these Notes should also apply to 12.1.x. I'll ensure that the Note owners update those references; thanks for letting me know about this.

Regards,
Steven

Posted by Steven Chan on February 05, 2010 at 12:47 AM PST #

Hi,
I´m trying to migrate a database of a EBS 11.5.9 from SOLARIS SPARC (9.2.0.8 64 bits) to LINUX-X86 (9.2.0.8 32 bits). Do you think EXPORT-IMPORT is suffcient to do this kind of migration? Did i need to pre-install in LINUX database all the products i´ve found in DBA_REGISTRY of original solaris database (ex: SPATIAL, JAVA, WORKFLOW)?
Best regards,
Sergio

Posted by Sergio Coutinho on February 07, 2010 at 09:45 PM PST #

hi Sergio -
You should be following the detailed note (Support Doc 230627.1) titled 'Export/Import Process for Release 11i DB Instances Using Oracle 9i Enterprise Edition'. This note covers the general database migration for 9i across platforms including those of different OS bitness and endian formats.
There are specific steps for the JVM, OLAP, etc. as a pre-install step (see Section 2) on the target platform prior to doing the import of the database on it (Section 3).
rgds,
John

Posted by John Abraham on February 09, 2010 at 09:04 AM PST #

Can we use datapump, or transportable tablespaces etc.. to speed up export/import process of DB migration, or they still not supported?

Posted by Raj on February 17, 2010 at 06:47 AM PST #

Datapump utilities (expdb/impdb) are certified with EBS and our current export/import process requires their use - datapump does offer advantages compared to traditional export/import (exp/imp) like increased speed, new features such as restarting from points of failures and parallel processing.

Transportable Database is a form of platform migration (for platforms of the same endian format) for the Database that is also certified with EBS - see:

* Using Transportable Database to migrate Oracle E-Business Suite Release 11i Using Oracle Database 10g Release 2 or 11g Release 1 (Doc 729309.1)
* Using Transportable Database to migrate Oracle E-Business Suite Release 12 Using Oracle Database 10g Release 2 or 11g Release 1 (Doc 734763.1)
* The MAA paper: Platform Migration using Transportable Database Oracle Database 11g and 10g Release 2

Transportable Tablespaces (for migration across platforms of different endian formats) is under review (see this call for Early Adopter Program participants - http://blogs.oracle.com/stevenChan/2008/08/call_for_xtts_eap_participants.html) and is not officially certified yet with EBS.

Posted by John Abraham on February 24, 2010 at 08:21 AM PST #

Tried explaining this to Sun guys? Tough job!

Posted by ss on February 25, 2010 at 02:15 AM PST #

Hi Steve,

We are planning to migrate the E-business suite (R12.1.3) from Solaris to Linux Platform,Current both database tier and Application tiers are on Solaris 10 paltform.

I have gone through the note ID 438086.1 for migrating the Application Tier from Solaris to Linux platform but i see a following restrictions in oracle note.

"The instructions in this document are for migration to a target UNIX/Linux platform. At present, Windows is only supported as a source platform.
"

So don't we have certified steps for migrating the E-business suit Application Tier from Solaris to Linux platform ?

Thanks,
Mohan

Posted by Mohan on September 28, 2011 at 12:46 AM PDT #

We had migrated an Ebs application from one platform to another platform with using your suggsted Document .. (238276.1)..
But we had seen a problem about interrupt customer working very long time while we worked on migration ..

As you know when we migrated database from source to target system then we should migrate Ebs from source to target too.
But we started to apply Document (238276.1) , we worked on this step ( 3. Clone the AutoConfig XML context file on the Target System )..

New Ebs system asked us which database will be your target database and we entered the database name but installation was stopped and we had an error ..
But after we had this error , we closed source ( on Sun Platform ) Ebs system then we tried to apply same step ( 3. Clone the AutoConfig XML context file on the Target System ) then system accepted our target database name and installation continued (on Aix system) ..

In this case , let me summarise the stituation ;

We applied step by step suggested document ..
This step forced us to shutdown source (on Sun Platform) Ebs system ..
Customers could not work anymore until we installed new Ebs systrm (on Aix Platform)..

Question :

How we can be succesfull without shutdown Ebs system (on Sun Platform) to end of the new Ebs system installation (on Aix system ..) ?

According to your suggested Document , we should shutdown source (on Sun Platform) apps tier services at 12 th step ..

Which step is the correct time to stop source system apps tier services ?

this step ?

3. Clone the AutoConfig XML context file on the Target System
The Clone Context tool will ask for all the new mount points on the Target migration node. Log on to the Target System as the APPLMGR user and run the following commands:

or this step ?

12. Run AutoConfig to complete the Target System configuration
$AD_TOP/bin/adconfig.sh contextfile=[TARGET SYSTEM CONTEXT FILE]

Note: The database will be updated to reflect the new Target System profile. Make sure all users are off the system and shut down the Source System application tier server processes. After this step, the Source System middle tier will no longer be available.

Maybe your answer would be 12 th step but we saw that Oracle installition process forced us to shudown source apps tier services at 3 rd step ....

Maybe we missed something or some special configuration ??

Which step is the correct time to stop source system apps tier services ?

this step ?

3. Clone the AutoConfig XML context file on the Target System
The Clone Context tool will ask for all the new mount points on the Target migration node. Log on to the Target System as the APPLMGR user and run the following commands:

or this step ?

12. Run AutoConfig to complete the Target System configuration
$AD_TOP/bin/adconfig.sh contextfile=[TARGET SYSTEM CONTEXT FILE]

Note: The database will be updated to reflect the new Target System profile. Make sure all users are off the system and shut down the Source System application tier server processes. After this step, the Source System middle tier will no longer be available.

Maybe your answer would be 12 th step but we saw that Oracle installition process forced us to shudown source apps tier services at 3 rd step ....

Maybe we missed something or some special configuration ??

Posted by guest on December 01, 2011 at 09:10 PM PST #

Hello -
In reviewing your basic assumptions, it is important to understand that one should think of application and database tier migrations as inherently different and separate. This blog article and the associated document (238276.1) states that this is clearly for application tier migration only - db tier migration involves an almost entirely different set of tools (export/import/datapump, Transportable Database, Transportable Tablespaces to name a few) and has a different considerations around endian formats, size of databases, etc.
If you are choosing to mix these two types of migrations, one should be careful to perform the database tier one first and then proceed with the application tier migration all in one single downtime, if your business can withstand that sort of outage. Proceeding with the database tier migration first and separately is our normal recommendation as that process can take up the most time.
With respect to your particular question about when the application services should be shut down, it should be done early and prior to Section 2 Step 3, specifically the step that instructs users to run the adclonectx script. A doc bug has been filed to add that to the instructions.
Regards,
John

Posted by John Abraham on December 06, 2011 at 06:11 AM PST #

Hi,
We need to upgrade apps and database so,
Put a production's clone to the new server

Upgrade from 11.5.9 to 11.5.10.2

Upgrade from 9.2.0.8 to 10.2.0.5

And finally upgrade to R12i

So ,we want know :
If the clone instance can become the new production instance without any data corrumption and we'll not need to make imp/exp data in this case ?
If yes can we clone the clone instance (new producton )to test instance (clone a clone instance )

Thanks for any guidelines or ideas

Posted by guest on February 09, 2012 at 06:15 AM PST #

Hi, Guest,

Check out this article for a pointer to a new whitepaper discussing this topic:

Best Practices for Combining EBS Upgrades with Platform Migrations
http://blogs.oracle.com/stevenChan/entry/oracle_e_business_suite_upgrades

Regards,
Steven

Posted by Steven Chan on February 09, 2012 at 10:06 AM PST #

Steven,

We currently have following configuration

11.5.10.2:
3 solaris8 nodes load balanced - forms+web tier
1 solaris10 node - concurrent tier + database

And we like to go to following configuration
Target (11.5.10.2):
3 Red Hat/Oracle Linux nodes load balanced - forms+web tier
1 solaris10 node - concurrent tier + database

Any experience with app tier on linux and cp tier+db on solaris? Does oracle support the target configuration above? I understand having to download same patch for solaris as well as linux. any other issues to consider?

Thanks,
-Hiren.

Posted by Hiren on June 28, 2012 at 08:59 PM PDT #

Hi, Hiren,

Sorry for the delay in responding to this.

It is possible to run different E-Business Suite nodes on different operating system platforms. The mixed-platform architecture you've outlined above is technically feasible.

The primary considerations are keeping everything organized, since now you need to research and apply different patches to different servers. We've heard of customers getting confused and trying to apply Linux patches to Solaris boxes. Using a tool like Oracle Enterprise Manager and Application Management Pack can help automate that.

Regards,
Steven

Posted by Steven Chan on July 16, 2012 at 08:24 AM PDT #

Hi,

We are planing to migrate the oracle EBS 11i to new machine as same os/config as source machine. So what method will be good for this migration ? as per my plan we like to use Rapid-clone.

steps are follows,

Step 1: Prepare the target system same as source system like OS, File system, Mount Points and packages.
Step 2: Prepare the source Instance for Pre-clone
Step 3: Shutdown the source instance
Step 4: Take the backup of source instance
Step 5: Move the Backup from source system to Target system
Step 6: Configure the clone on target system
Step 7: Configure the post clone activities like work flow mailer

Posted by guest on March 26, 2014 at 02:58 AM PDT #

Guest,
The methodology outlined above, is used to migrate EBS from one platform to another. For example, from Windows to Linux.
In your case, it looks like Source and Target will have the exact Operating system and OS configuration. For this use case, you will simply use standard Rapid Clone source-to-target cloning flow. For 11i, this is fully documented in Note 230672.1.

Posted by Max Arderius on March 28, 2014 at 08:58 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today