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

Can You Share EBS Database Homes?

Steven Chan
Senior Director

No. The Oracle E-Business Suite database ORACLE_HOME cannot be shared between multiple EBS instances.

The Oracle E-Business Suite database ORACLE_HOME must be used exclusively for a single EBS database.  It cannot be shared with other Oracle E-Business Suite instances or other applications.  This applies to all EBS releases, including EBS 12.1 and 12.2.

Why does this restriction exist?

Configurations, log files, and more must be unique to a given instance.  Existing tools are designed to work with the a single database associated with a single application.  For example, the EBS pre-clone tool creates a clone directory that is related to a specific database.  AutoConfig is designed to run for a particular application+database combination.

What are the support implications if you ignore this restriction?

Running these tools in an environment where multiple applications are associated with a single database ORACLE_HOME will have unpredictable results.  If you report an issue whose root cause is found to be due to the sharing of a single database ORACLE_HOME between multiple EBS instances, our default recommendation would be to revert to a configuration where each EBS instance has its own database ORACLE_HOME.

Oracle will produce patches only for issues that can be reproduced in an environment where a single database ORACLE_HOME is associated with a single EBS application. 

Join the discussion

Comments ( 5 )
  • guest Tuesday, March 7, 2017

    Please can you comment on the following statement which appear in several MOS notes on this issue (references below).

    "Note: If you are using shared Oracle Home then TNS_ADMIN cannot be shared as the directory path must be same on all nodes.See Appendix F for an example of how to use SRVCTL to manage listeners in a shared Oracle Home."

    Since they explain how to do it, doesn't implicitly mean that is allowed?

    Using Oracle 12c Release 1 Real Application Clusters with Oracle E-Business Suite Release 12(Doc ID 1490850.1)

    Using Oracle 11g Release 2 Real Application Clusters and Automatic storage management with Oracle E-Business Suite Release 12.2(Doc ID 1453213.1)

    Using Oracle Real Application Clusters 11g Release 2 with Oracle E-Business Suite Release 12(Doc ID 823587.1)

    Using Oracle 12c Release 1 (12.1) Real Application Clusters with Oracle E-Business Suite Release R12.2(Doc ID 1626606.1)

  • -Dan Tuesday, March 7, 2017

    Well this catches us a bit off guard. How long has this restriction been in place? Have any customers actually reported problems?

  • Steven Chan Friday, March 10, 2017

    Hi, Dan,

    Hope you've been well!

    This isn't new. EBS tools are all designed this way.

    Pragmatically speaking, this hasn't been a problem reported by customers. It is a FAQ, though, which is why I highlighted it here as a blog article.



  • guest Monday, March 13, 2017

    Hi Steve,

    All the setup done by Autoconfig seems to be segregated by context name that includes the instance name, so I don't see why this restriction is in place.

    The separation of the configuration seem to imply it is possible to share the ORACLE_HOME between different instances, even if this is not supported on the customer installation?

    I understand that this is very different scenario from a shared oracle home across an Oracle RAC cluster used by a single EBS instance, which should be supported following the notes posted by Guest previously.

    Best Regards,

    Luis Freitas

  • Govind Batte Friday, January 12, 2018
    We are in building ESB databases, checking the feasibilities
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.

Recent Content