Sharing Apps R12 File Systems Across Multiple Databases

One of the challenges an IT manager faces today is managing complex application configurations from development to production. This becomes a monster challenge with the proliferation of environments with multiple application and database tier nodes.

Oracle E-Business Suite Release 11i and 12 provide flexibility in laying out file systems via a Shared File System option. A Shared File System stores application tier files on a shared disk storage that can be accessed by multiple application tier nodes. Shared File Systems have the potential to lower your Total Cost of Ownership (TCO) by reducing your maintenance and hardware requirements.

Note: Shared File System is  not supported on MS Windows platform

New Features in E-Business Suite R12

Release 12 Shared File System configurations allow several deployment options. Some of the key features include:
  • The ability to have multiple nodes running each of the following service types:
    • Forms
    • Web - in a load balancing configured option
    • Concurrent Processing (Batch) - in a Parallel Concurrent Processing configured option
  • Read-only node implementation for Forms, Web, Concurrent processing
In addition, a new configuration option introduced in Release 12 has the potential to save significant time and resources for an Applications DBA:  the ability to share applications tier file systems across multiple database instances.

Sharing Applications Tier File Systems Across Multiple Database Instances

Release 12 customers can now install and configure the application tier file system on a central machine that is used by two or more database instances. This configuration option is useful in cases where you would like your test and development environments to share the same applications tier file system. 

Shared File System across DB:

Minimum Requirements
  1. This option is only valid for the Applications tier file system and not for the database tier file system

  2. All the database instances are patched up to the same level

For a walkthrough and other details required for this configuration and deployment option,  see: [Editor: Sharing application tier file systems between multiple environments has the potential to reduce your overhead but is the IT equivalent of placing all of your eggs in a single basket.  If the shared file system goes down, multiple Apps environments are impacted.  Accordingly, prudent system administrators should put backup and recovery procedures in place for shared servers.]

Related Articles


Hi Steven,

Worth mentioning when applying a patch you patch the primary instance first, then patch the remaining instances with:
$ adpatch options=nocopyportion,nogenerateportion,nocompilejsp

In single shared multi db configuration can adpatch across multiple nodes be run in parallel?


Posted by Gareth on January 29, 2008 at 01:44 PM PST #


Thanks for your comment. I will update the note. I do not think parallel adpatch run is supported.

Posted by Prasad Akkiraju on January 30, 2008 at 08:09 PM PST #


The note is already there in the Metalink Note. Hence, not adding it in the blog as it is specific configuration step. Also, adpatch parallel run is not supported.

Posted by Prasad Akkiraju on January 30, 2008 at 11:09 PM PST #


I am new in oracle apps, i have a big trouble because the user ask me to load the master items and locators from a flat file separated by ",", i do not how to do it, do you have any script to perform the initial load into the application ?.

What tables names must are used to do this?.

Thanks in advance for your help.

Posted by Alberto Luna on January 31, 2008 at 03:19 AM PST #

Hi, Alberto,I'd recommend your logging a formal Service Request via Oracle Metalink to get assistance with this one.  Good luck with your implementation.Regards,Steven

Posted by Steven Chan on January 31, 2008 at 09:03 AM PST #


Just wondering if sharing of the application file system is acceptable between production instances, assuming the customer in question is willing to accept the inherent risks of using this in their production environments.

I am currently working with a customer who has several dozen Ebiz production environments (all at the same patch levels) who is wondering if they can use this method to reduce the number of distinct file systems.

I'd appreciate your view on using this method for this purpose.


Posted by Bhavin on February 09, 2010 at 04:25 PM PST #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2015