X

The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

Can EBS Nodes Be at Different Operating System Levels?

Steven Chan
Senior Director

Oddly, a category of EBS architecture questions that I'd thought long-settled is starting to reemerge.  I've recently seen several queries along the lines of:

  1. Can EBS database nodes and application tier nodes be on different operating systems?
  2. Can multiple EBS database nodes be on different operating systems or levels?
  3. Can multiple EBS application tier nodes be on different operating systems or levels?

Here are the answers to these questions:

1. Can EBS database nodes and application tier nodes be on different operating systems?

Yes.  In some cases, the operating systems certified for EBS database nodes cannot be run on the application tier. These are called "database tier only" certifications. It is quite common to see this configuration, especially in large EBS environments.

2. Can multiple EBS database nodes be on different operating systems or levels?

No.  From our "Installation Guide: Using Rapid Install" documentation:  

"All database tier nodes must be at the same operating system patch level."

3. Can multiple EBS application tier nodes be on different operating systems or levels?

No. From our "Installation Guide: Using Rapid Install" documentation:  

"All application tier nodes must be at the same operating system patch level."

Here's a screenshot from our EBS 12.2 documentation (emphasis in red):

References

Related Articles

Join the discussion

Comments ( 4 )
  • Robin Chatterjee Tuesday, May 30, 2017
    Hi, But since you certify based on major number only i.e certify for 5.x or 6.x why should it matter if one db node is at 5.5 which another is at 5.11 or one application node is at 6.1 while the other is at 6.11 . I can see cases for example rolling upgrades where running this configuration temporarily would be of benefit. Rapid clone really doesn't have any minor patchnumber dependancy that I can see. In fact I suspect there is no major patch number issue either i.e I can quite likely clone from OEl 5.x to OEL 6.x without any issues as we have done it in the past when upgrading our OS. so this
    document actually needs more clarification.
  • Catharine Winden Wednesday, May 31, 2017
    Hi Steven,
    I timely topic as I was just contemplating this today.... Just to stretch to discussion.... We have two shared appl tops, one for internal users with two server, and one for external SS users with 4. We are on Linux 5, but would like to up to 7. Can we upgrade the SS appl top and nodes only and leave the internal appl top and nodes on 5 until we gain confidence with 7? thanks catharine
  • Steven Chan Thursday, June 1, 2017
    Hi, Robin,

    Thanks for the feedback on our documentation. There are hidden dependencies on the back end (i.e. in various AD/TXK tools) that are not easily visible to sysadmins or users. We'll get that clarified.

    We do not recommend a rolling upgrade process where different nodes run at different levels. We will issue EBS patches only for issues that can be reproduced in environments where all nodes are running at the same operating system patch level.

    Regards,
    Steven
  • Steven Chan Thursday, June 1, 2017
    Hi, Catharine,

    No, we would not recommend the configuration you've described. As noted in the article above, all EBS nodes at the same level (in your case, the application server tier) must be at the same operating system patch level. This is true regardless of whether the application servers are internal and external.

    Regards,
    Steven
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.