The Scoop: Oracle E-Business Suite Support on 64-bit Linux

Linux tux-large.jpg
This article addresses frequently asked questions about Oracle E-Business Suite (EBS) 64-bit Linux support.

Q:  Which 64-bit Linux OSs are supported for EBS?

A: Beginning with Release 12, we support the following 64-bit operating systems for both application and database tiers on x86-64 servers:

  • Oracle Enterprise Linux
  • Red Hat Enterprise Linux
  • SUSE Linux Enterprise Server
For EBS Release 11i (and again in Release 12), when the application tier is installed on a certified platform, additional platforms (including the above) may be used for a 64-bit database tier on x86-64 servers. This is an example of a mixed platform architecture (Release 12), or a Split Configuration (Release 11i).

Q:  I understand that the EBS application tier code is 32-bit, even for the 64-bit Linux OS -- is this the case?
A: It is true that the majority of executables provided as part of our release media on the application tier are 32-bit (as are the Fusion Middleware libraries and objects they depend on).  However, the 'Planning' products have large memory requirements and therefore are 64-bit compiled to take advantage of the larger memory space afforded by the 64-bit OS'es.

Q:  How do I install EBS on 64-bit Linux?
A:  For new installations of EBS Release 12 on supported 64-bit Linux operating systems, you can use Rapid Install as directed in "Oracle Applications Installation Guide: Using Rapid Install" to install the database and application tiers.

For Database Tier Only platforms in a mixed platform architecture, you can use Rapid Install as directed in "Oracle Applications Installation Guide: Using Rapid Install" to install the database and application tiers on supported platforms, and then migrate the database tier to a certified 64-bit operating system.

Q:  How do I migrate EBS Release 12 from 32-bit Linux to 64-bit Linux?

A:  Please refer to Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit (Note 471566.1) for instructions on how to migrate EBS from 32-bit to 64-bit Linux.

Q:  How do I migrate an existing EBS database to 64-bit Linux?

A:  To migrate an EBS database to a certified 64-bit Linux operating system on x86-64, refer to one of the following documents:

For EBS Release 11i:

For EBS Release 12:
Q:  How do I migrate EBS Release 12 on a non-Linux platform to 64-bit Linux?
A:  There is no documentation that covers the direct migration from a Windows or UNIX application tier directly to 64-bit Linux.  However, the document Application Tier Platform Migration with Oracle E-Business Suite Release 12 (Note 438086.1) contains instructions for migrating to 32-bit Linux, and Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit (Note 471566.1) contains the additional steps to configure your environment for 64-bit Linux.  Pondering this question just now gave me the idea to write a new white paper, which will presumably eliminate several steps from either document and insure a smooth migration process.  Stay tuned to this space for more information on this upcoming paper.

Q:  How do I patch EBS on Linux 64-bit?

A: The EBS 32-bit Linux application tier patches are applicable for 64-bit Linux OSes as well.  From the Oracle support portal, you can do a search by patch number to bring up the 32-bit patch.  Note that if you click on the informational icon to the left of the Platform pulldown menu for this patch, it brings up a page stating:

For Oracle Applications Release 12 on Linux x86-64, queries will return a Linux x86 patch. This patch may be applied to both 32-bit and 64-bit operating systems.

Q:  What are the benefits of running EBS Release 12 on 64-bit Linux?

A: Theoretically, 64 bit architectures allow for "2 to the 64th power" bytes or 16 exabytes of RAM, and while individual operating systems and hardware architectures impose constraints (for instance, the maximum RAM is 1 terabyte on x86-64), you are unlikely to hit this memory limit with today's applications. 

For 32-bit compiled code, even though the process address space is limited to approximately 3 GB (even on the 64-bit OS), with overall addressable space up to 1 terabyte you'll be able to run many more processes.  This is an excellent model all around for larger customers wanting to consolidate their hardware or scale up.

Q:  Can we (or why can't we) run EBS Release 11i on 64-bit Linux?

A:   We support the use of 64-bit Linux OS'es in the EBS database tier in a 'split configuration' or 'database tier only' configuration for 11i, wherein the application tier can be on any certified EBS platform and the database tier can run additional database certified platforms (like 64-bit Linux).  Customers wanting headroom for the RAM-intensive DB processes can run their database tier on Linux 64-bit (in a split tier configuration), and if needed spread the application tiers (CM, Forms, Web) across multiple middle tier machines to distribute the load amongst the 32-bit OS'es.

As to why we do not support EBS Release 11i on 64-bit Linux, there are several reasons:  a)  it doesn't "just run";  b) there is no third party support; c) given the costs, we chose to chose to focus our resources on EBS Release 12 and beyond.  Let me explain.

Contrary to what you might think, you cannot necessarily run 32-bit code on 64-bit Linux without a bit of tweaking.  On the technical front, you would need to install the 32-bit OS libraries and deal with potential conflicts between 32-bit and 64-bit OS packages, including file overwrites.  Note that when we introduced 64-bit OS support in EBS Release 12 we made changes to all of the product makefiles, carefully analyzed and laid out both the 32-bit and 64-bit package dependencies, modified installation, configuration and cloning software for OS recognition and proper file locations, and conducted extensive testing.  Each new release requires this process to be repeated, and each new release package requires an independent packaging effort.

In addition, for 64-bit Linux support we've established a 64-bit infrastructure across Oracle teams (in support, engineering, release, QA and certification teams).  This infrastructure investment was made for EBS Release 12 and higher.

Also note that EBS Release 11i has an aging technology infrastructure, and neither Oracle nor third party tool versions used in EBS Release 11i are explicitly supported on the 64-bit operating system in 32-bit mode.

Call us old-fashioned if you will, but given these limitations, because of our support commitment to you and what's behind that commitment we will only support EBS Release 12 forward on 64-bit Linux.

Related Articles

Great article. Thanks.

One question. I currently run 11i in a split tier config (11gR2 DB on RHEL 5.4 64-bit, Apps tier on RHEL 5.4 32-bit). We are beginning (finally!) to do our project plan for migration to R12 and plan on running RHEL 5.5 64-bit throughout. In your post, you reference note 461566.1 on migrating R12 from 32-bit to 64-bit, but I'm going from R11 32-bit to R12 64-bit (app tier). Is there a documented procedure for that migration or do I need to first go R11 32-bit to R12 32-bit and then turn around and do R12 32-bit to R12 64-bit?

I admit, I haven't done much research on this but I imagine many clients have / will be in this exact predicament.

Thanks in advance,

Posted by Jay Weinshenker on April 16, 2010 at 07:44 AM PDT #

Hi Steven,

This is a very informative article and Thanks for posting it.
I have couple of doubts on the same but a bit different topic -- we are in the process of configuring 11i Applications with 11gR1 RAC on a split-tier configuration on OEL 5 and we are facing an issue with the CP node/failover concept.
Our architecture is: 1 Applications tier (OEL 5 32-bit) on a 2-node RAC Database (OEL 5 64-bit)
My doubts are:
1. Is it possible to configure the CCM with the Failover aspect for the Database through PCP (with only 1 Application tier only)?
2. If there's a possibility, how to define the Failover for the CCM as the DB is on 64-bit?
3. Does installing the Applications tier on a different 64-bit O/S resolve the CCM Failover from the database node1 to node2

Thank you.


Posted by Panda on April 21, 2010 at 01:54 AM PDT #

Hi, Panda,

I'm afraid that I don't know, but I'll ask someone in our Applications Platforms Group to take a look at this. In the meantime, your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.


Posted by Steven Chan on April 27, 2010 at 02:23 AM PDT #

Jay- Sorry for the late response. Regarding going from 11i 32-bit to R12 64-bit, you *can* migrate during your upgrade. During the upgrade when it says to lay down the new R12 appl_top, you would install the 64-bit appl_top using the Linux x86-64 distribution. If you have specific questions after reviewing the R12.X Upgrade documentation, then please email us back.


Posted by Terri Noyes on April 27, 2010 at 03:46 AM PDT #


It appears that your concurrent processing runs on the single application tier, and you want to know if it can be configured to fail over to the 64-bit DB tier. The answer is unfortunately no -- the 11i CP code (and all the application tier code) is not certified to run on 64-bit Linux. A configuration that supported CP failover with PCP in 11i would therefore need to have a second application tier node.

Please let me know if I've answered your questions.


Posted by Terri Noyes on April 27, 2010 at 10:38 PM PDT #

Thank you for the advice and help, Terri.
We also came to the same conclusion as yours after some more discussions.

Best Regards,

Posted by Panda on April 29, 2010 at 12:58 AM PDT #

Hi Stephen,

Firstly, thanks for an excellent blog - a number of your articles have been of huge assistance to me in the past.

We are currently doing an EBS 11 deployment on a split tier RHEL 5.4 - 64-bit backend DB and 32-bit application tier. Unfortunately, moving to R12 isn't an option at this stage which ties us into a 32-bit application tier.

We were intending to run >16GB of memory (actually ~64GB) on our application servers. However, I've recently found our Red Hat have discontinued the "hugemem" kernel on RHEL 5 and 16GB is the maximum addressable space now (there was a bug in the RH docs which still alluded to 64GB being the maximum until recently).

So, we're faced with having to go back to RHEL 4 and the shorter support life that entails.

I'm just wondering if you had any advice or feedback of how you see customers using larger memory systems for their R11 application tiers?

Thanks in advance,

Posted by Andrew S on May 24, 2010 at 08:05 AM PDT #

Yes, getting very large memory capacity on 32-bit Linux is a challenge. I will discuss with our Linux engineering team to see if there are alternatives to rolling back to RH4, barring adding a box or two, which is very common practice.

Posted by Terri Noyes on May 24, 2010 at 08:27 AM PDT #

Hi Stephen,

I am currently using Oracle application with RDBMS on two tier (Apps Tier & DB Tier) Windows platform. I wanna migrate it to LINUX.

I am confiused which Tier first to migrate either database or apps.

Doc ID 238276.1 migrate application 11i
Doc ID 230627.1 migrate database 9i

Plz help me out.


Syed Shabuddin

Posted by Syed Shabuddin on June 22, 2010 at 09:19 PM PDT #

It is customary to migrate the database tier first. Go ahead and migrate the database using Note 230627.1, then migrate the application tier using 230627.1.

Note 230627.1 Section 2 steps 6,7 (and other autoconfig-related steps) require a database connection to be available, so this way the migrated database is all set up and ready for the new app tier.

It can be done in reverse (going to an interim config with db tier staying on Windows and application tier on Linux), but this would create more work and I don't see any upside.

Posted by Terri Noyes on June 23, 2010 at 03:43 AM PDT #

Hi Steven,
Presently, our ebusiness architecture is :
- database tier+concurrent mgr ( server one),
- apps tier (server 2),
- apps tier (server 3),
- external Irecruitment (server 4)
All of them are using redhat 4 linux 32 bits.
Because performance problem, we plan to upgrade all these servers to redhat 5, and split the database tier to a new brand server redhat 5 / 64 bits.
My question:
- Does the concurrent mgr work separatly from database tier?
- I saw a problem on " iRecruitment with Linux on IBM System z: there is a known limitation with the use of filters in searching and displaying certain documents in iRecruitment". Do you think it will be ok for HP linux?


Posted by Mai on October 14, 2010 at 10:22 AM PDT #

The concurrent manager shares the characteristics of the application tier support. Since 11i is not supported on Linux 64-bit, you will need to move the concurrent manager to the application tier.

There are different My Oracle Support articles for migrating your 11i database tier, depending on which version of DBMS you are on:

Using Oracle Applications with a Split Configuration Database Tier on Oracle 11g Release 2 (946413.1)
Using Oracle Applications with a Split Configuration Database Tier on Oracle 11g Release 1 (562983.1)
Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 2 (369693.1)

Note an iRecruitment issue listed for System z will be unique to System z. Our Linux support on Intel-based processors and machines from HP, Dell, IBM, etc. is separate from System z.

I hope I've answered your questions- feel free to send more my way.


Posted by Terri Noyes on October 15, 2010 at 01:13 AM PDT #

Hi Terry,
Thanks for your answer.
As I have 2 apps tier in load balancing and they are both actif?
I'd like to know if we could configure ebs with 2 concurrents manager up the same time on 2 apps tier ?


Posted by Mai on October 15, 2010 at 03:53 AM PDT #

Hi Terri
Can you please elaborate on the steps to migrate from 11i 32-bit to R12.1 64-bit during the upgrade.


Posted by Pieter Viljoen on January 05, 2011 at 08:38 PM PST #

Hi Pieter-
Without knowing your particular details, my thought is that you may want to migrate the database (and upgrade, if required, to the desired level). Get that all working and tested, and then follow the normal upgrade procedure. On page 2-28 of the upgrade manual where it calls for the Rapid Install of the new application tier, this is where you lay down the 64-bit application tier code.

I suggest you ping Nick Quarmby, who wrote the platform migration primer on this blog, to discuss any particular scenario.


Posted by Terri Noyes on January 10, 2011 at 01:20 AM PST #

We have R12 Upgrade Project with 2-phases:
Phase 1:- Upgrade existing eBiz 11i/10gR2 to R12 /10gR2 on Sun Solaris
Phase 2:- Convert Sun Solaris to HP SUSE Linux platform.

Now, we are in the process of combining both phases to-gather, hence we started the research about approaches , paths & certifications, best method to build R12 instance on Linux platform with reasonable downtime.

Current :
Platform:- Sun Solaris: -Solaris [tm] OE (64-bit) with Big Endian format
Database: 10gR2 (
E-Biz : 11.5.9 (2-Tier:- db+ccm tier & app tier)

Platform: HP SUSE Linux version 10 (Linux x86 64-bit with Little Endian format)
Database: 10gR2 ( with RAC
E-Biz: R 12:- 12.1.3 (3-Tier: dbtier & app+ccm tier 1 & 2)

My initial thought process about the approach is:

1. Rapid Install of R12 with seed database on New Linux servers.
2. Transport & convert 11i database (10gR2) to New Linux servers.
3. Apply R12 (12.1.1) database driver on 10gR2 database.
4. Apply 12.1.3
5. Configure the - RAC

Is this approach feasible & possible?

In general, it make sense to go to 11gR2 since rapid install brings 11g version, But which one is the best approch for platform conversion out of from 10gR2 to 11gR2 or 10gR2 to 10gR2 ?

We are going thru so many Questions & If. Then’s… like...

What do you suggest the best approach would be in my case?

Thanks in advance,

Posted by Sridhar Bommareddy on January 18, 2011 at 04:52 AM PST #

Hello Sridhar -
I can appreciate the complexity that you are facing - I will preface my recommendations by saying that they are general and based on our own experiences while your specific situation may require professional (i.e. Consulting or your own internal) analysis to minimize risks and downtime.
The general steps would entail
1a. Installing the Oracle Database 10g as a standalone on the target machine.
1b. Migrating the EBS data from source to the target (using datapump export/import or for large databases, transportable tablespaces).
2. Installing the EBS 12.1.1 application tier on the target machine using the Rapid Install Upgrade option and running the R12 upgrade driver (following the R12 Upgrade Guide)
3. Installing the 12.1.3 RUP
4. Configuring RAC

A couple of points to be made:
(a) Each of these steps (1->3) can be viewed as discrete and the system can be brought up if needed between each step (in order to minimize downtimes).
(b) Note that 12.1.1 brings in 11gR1, so if you'd like to go to 11gR2, you'd still need to perform that DB upgrade as a post EBS upgrade step.

As always with these complex processes, extensive testing of the final path chosen is critical..


Posted by John Abraham on January 21, 2011 at 01:43 AM PST #

Thank you for recommendation. I am outlining the approach pretty much the way you’d described. Our DB is ~3 TB in size with OATM, Thinning of adding split configuration for after Data migration to Linux server to validate the DB migration step using existing Apps on Oracle/sun Solaris machines.

It would have been nice if XTTS can work directly from (Solaris) 10gR2 to (Linux) 11gR2? Do you know if this option is available now or coming in future?

Best Regards,

Posted by Sridhar Bommareddy on January 25, 2011 at 05:14 AM PST #

hi Sridhar -
The current 11i XTTS process only supports a 10gR2 -> 10gR2 migration. We are looking at a future (perhaps R12) XTTS process supporting an upgrade as well but cannot commit to it currently given the added complexity. Please feel free to touch base with me periodically in the future and I will also track your request as part of a justification for this effort.

Posted by John Abraham on January 25, 2011 at 08:08 AM PST #

Hi John,

One of the pre-requisite in Metalink note 454574.1 Cross Platform Transportable Tablespaces on 11i with 10gR2 [ID 454574.1], indicating that Oracle EBS apps tiers must version.
• The Oracle E-Business Suite application tiers of both source and target systems must be version
But, we are on 11.5.9. do I have to upgrade prior to Linux migration?

Best Regards,

Posted by Sridhar Bommareddy on January 27, 2011 at 05:58 AM PST #

Hi Sridhar -
yes, as noted in the XTTS doc, is a prerequisite for the use of transportable tablespaces.

Posted by John Abraham on January 28, 2011 at 01:29 AM PST #

Hi Steve,

Thanks in advance. Following is my new install going to look like for EBS R12.1.3:
i. AIX 6.1 (64-bit) : RDBMS only
ii. OEL 5.7 (64-bit): Techstack only

I was wondering if I can install everything on Linux and then migrate the DB to AIX.
Q: Can or is this possible? If yes, then can you point me in the direction of the MOS article for this, as I am unable to find anything that tells me how to achieve this. Everything is pointing towards migration to Linux?

Please advise....

Posted by Vasu Ranganathan on December 18, 2011 at 12:07 PM PST #

Hello Vasu -
For fully certified platforms such as these (as opposed to database tier only platforms), you can use the Rapid Install media available for each platform to install the database tier and application tier nodes respectively (see multi-node installation in our Install guides).
While you could certainly install everything on Linux, you would then have to separately install the DB on the AIX target and then migrate EBS data over to the platform using a data migration process such as export/import. From a time and disk space perspective, this will likely be less optimal.

Posted by John Abraham on December 19, 2011 at 08:34 AM PST #

Hi Steve,Terri

We have a Single Node Configuration with both Apps and Db Tier on the same node.
The H/w is IBM 64 bit , but we run Rhel 4 32 bit , and 11i / 9i Db on the same.

Recently we are planning to Jump to a 64 bit H/w and 64 bit Rhel , with R12. Up gradation and Reimplementation are the options.

Considering the Technical Situation now in Oracle , Is an up-gradation possible? What are the steps ?

Or we have to fall back only on re implementation ?


Posted by Vithal Salgaonkar on March 04, 2014 at 10:37 PM PST #

Hello Vithal -
From a purely platform migration point of view, a re-implementation is not necessary going from 32bit hardware to 64bit.
My recommendation is that you should first upgrade and then migrate the database to 11gR2 on the 64bit hardware - this is a standard 'split tier' configuration that is highlighted in MOS Note 946413.1).
After doing so (preferably in an earlier downtime), you would then follow the standard R12 upgrade to put down the new R12 application tier on the 64bit hardware, etc. to upgrade to R12.
Please also review the article that I'd written previously on the topic:
Best Practices for Combining EBS Upgrades with Platform Migrations (

Posted by John Abraham on March 05, 2014 at 11:33 AM PST #


We are currently running database and application on RHEL 4 for our EBS, we are planning for migrating it( same setup ) to new latest OS(RHEL) like RHEL 6.2, So for the above requirement can you guide me how to achieve this ?

Thanks & Regards,
Chandrasekar S

Posted by guest on May 09, 2014 at 04:53 AM PDT #

Is it possible to install Oracle EBS r12.1.1 Applicaition on Linux 64 bit an and database is on Sun solaris 64 bit

Posted by guest on March 23, 2015 at 10:29 PM PDT #

Yes, that's possible - it's a more general case of a 'split tier' or mixed platform architecture where for a new install, you'd install EBS (app and DB tiers) on Linux and then migrate the DB over to Solaris.

Posted by John Abraham on March 25, 2015 at 08:38 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016