Sharing The Application Tier File System in Oracle E-Business Suite Release 12.2

The most current version of this document can be obtained in My Oracle Support Knowledge Document 1375769.1.

There is a change log at the end of this document.

Note:

Sharing the application tier file system is not supported on application tier server nodes running Windows.

Section 1: Overview
1.1 Concepts and Terminology
1.2 Oracle E-Business Suite Release 12.2 Architecture
1.3 Oracle E-Business Suite Release 12.2 File System Layout for Shared Application Tier

Section 2: Planning Deployment Options

Section 3: Configuring a Shared Application Tier File System with 12.2 Rapid Install
3.1 Install the Database Tier on Node 1
3.2 Install the Primary Application Tier on Node 2
3.3 Execute the Adpreclone Utility on the Run and Patch File System

Section 4: Adding a Node to the Shared Application Tier File System
4.1 Export the Required Application Tier File System From the Primary Application Tier Node
4.2 Mount the Application Tier File System on the Secondary Application Tier Node
4.3 Add the Secondary Application Tier Node to the Farm

Section 1: Overview

1.1 Shared Application Tier File System Concepts and Terminology

You can configure multiple application node machines working with a single Oracle E-Business Suite database node. This creation of a "multi-node" Oracle E-Business Suite instance is frequently done to lower cost of ownership (many small machines are cheaper than one big one), increase fault tolerance (one machine fails, others do not), or scale the instance (support more users and a greater load).

When configuring Oracle E-Business Suite to use a shared application tier file system, the application tier node can be configured to perform any of the standard application tier services, such as Forms, Web, and Concurrent Processing (Batch).

Note the following definitions:

Node

A node is a logical set of processes running on one hardware machine. Sometimes a node is also referred to as a "server" or an "instance". In a single-node installation of Oracle E-Business Suite, all the applications processes (including the database processes) run on one node, whereas in a multi-node installation, the processes are distributed across multiple nodes.

A multi-node installation of Release 12.2 supports both shared and non-shared application tier file systems. An application tier file system consists of:

APPL_TOP file system (APPL_TOP and COMMON_TOP directories).
Application tier technology stack file system (OracleAS 10.1.2, Oracle WebLogic Server, and WebTier Oracle Homes).
Instance Home (INST_TOP) file system. Each application tier has a unique Instance Home file system associated with it.
OraInventory directory, which stores information about all the components installed in various Oracle Homes

Service

A service is a functional set of Oracle E-Business Suite application processes running on one or more nodes. Where applicable, the term 'service' replaces the more traditional term of 'server'.

Application Tier Services

The following are the major application tier services:

Root services
Web Entry Point services
Web Application services
Batch Processing services
Other services

Primary Application Tier Node

A primary application tier node is the first (and perhaps only) application tier node where the APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, WebLogic and the WebTier Oracle Home are installed and configured.

Secondary Application Tier Node

A secondary application tier node is an additional application tier node where the APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, Oracle WebLogic Server and WebTier Oracle Homes are visible and configured.

The APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, Oracle WebLogic Server, and WebTier Oracle Home file systems are mounted on this node either from the primary application tier node or from an NFS server.

Instance Home

The Instance Home is the top-level directory that contains all the instance specific files associated with an application tier node (APPL_TOP and OracleAS 10.1.2 Oracle Home files). In a shared file system, each application tier will have a unique Instance Home.

1.2 Shared Application Tier File System Architecture

The Oracle E-Business Suite Release 12.2 architecture is a framework for multi-tiered, distributed computing. In this model, various services are distributed among multiple levels, or tiers, as shown in the figures below. Refer to Oracle Applications Concepts in the Oracle Applications Documentation Library to learn more about Oracle E-Business Suite architecture.

In a shared file system, all application tier files including the instance_top are installed on a shared disk resource, which is mounted on each application tier node. Any application tier node can be configured to perform any of the standard application tier services, such as Forms, Web and Concurrent Processing (Batch) services. All changes made to the shared file system are immediately accessible to all application tier nodes.

Note:

All application tier nodes in a shared file system must be running the same operating system.
Shared Application Tier File System can not be a read-only-file system unlike in the previous releases.

Note for customers using OCFS2 File System:

It is recommended to format the OCFS2 file system for the application tier with the default block size and not use larger block sizes supported by OCFS2. Refer to OCFS2 Best Practices Guide for more information.

General Three Tier Architecture

Application/Database Tier Components

Release 12.2 Dual File System Setup on a Single Tier

1.3 Shared Application Tier File System Layout

When setting up Oracle E-Business Suite to use a shared application tier file system, an application tier node can be configured to perform any of the standard application tier services, such as Forms, Web, or Concurrent Processing (Batch).

An application tier will have a unique Instance Home associated with it. The instance home can be placed at the default shared location as configured by rapid install/rapid clone or can be relocated to a local disk on the respective application tier. Oracle recommed the instance home to be configured on the shared disk.

Note: The following must all be true In a shared file system:

User ID and Group ID should be consistent across all nodes to avoid file access permission issues.
The same absolute path must be retained for the shared file system mount points on each node.
The value for the context variable "s_atName" must be same across all the application tier node context files.

Section 2: Planning Deployment Options

Shared Application Tier File System is the preferred deployment model for Oracle E-Business Suite Release 12.2.

In Release 12.2, two application tier file systems are installed on the primary application tier node. Provided to support online patching, they are known as the run file system and the patch file system. The run file system is where the application tier processes are run from. The patch file system is used by the adop (AD Online Patching) utility to update Oracle E-Business Suite code and configuration during an online patching cycle.

Note: The role of the two file systems swaps after each patching cycle, with what was the patch file system becoming the new run file system, and what was the run file system becoming the new patch file system.

For more information about online patching, refer to Oracle E-Business Suite Concepts and Oracle E-Business Suite Maintenance Guide.

Section 3: Configuring Shared Application Tier File System with Release 12.2 Rapid Install

This section describe the steps an administrator need to perform to prepare for a shared file system installation. The Rapid Install utility only lay out a primary application tier . The subsequent nodes that share the file must be added using the add node utility as described in the section 4 of this document.

The 12.2 Rapid Install utility can be used to install a new, fully configured Oracle E-Business Suite system, including the latest certified Oracle E-Business Suite technology stack and all patches, product family release update packs, release update packs, and other updates available at the time of this Oracle E-Business Suite release. Rapid Install employs a wizard (RapidWiz) that guides you through the screens used to carry out the selected task. On the wizard screens, you enter configuration values for your system.

The Rapid Install utility supports single node installations (where the database and the application tier are installed and configured on one machine), and multinode installations (where the database and the application tier nodes are spread across different machines). Refer to Oracle E-Business Suite Installation Guide: Running Rapid Install for more information.

This document describes a two node installation scenario, where the database tier is installed on node 1 (primary database tier node) and the application tier is installed on node 2 (primary application tier node). The steps below show the sequence needed to complete the installation.

Note: It is recommended that you stage the installation software on a remote file system that can be mounted and accessed from the different nodes on where you are going to perform the installation.

3.1 Install the Database Tier on Node 1

Start the RapidWiz utility on node 1. The first screen lists the components that are included in, or supported by, this release of Oracle E-Business Suite. You can see from this list that a new installation includes a fresh Oracle 11g Release 2 (11gR2) database. Enter the appropriate values as prompted by the Installer for the database and the application tier nodes, and complete the database tier installation.

Note: When entering the location of the install directories for the application tier install, you can either enter the location of a local drive on the machine, or an NFS location that is accessible from the primary application tier node. The recommendation is to install the application tier file system on to a remote file system that can be mounted across various application tier nodes.

3.2 Install the Primary Application Tier on Node 2

Start RapidWiz on node 2. The database and associated database tier processes must be running to complete this installation successfully. The first screen lists the components that are included in, or supported by, this release of Oracle E-Business Suite. You can see from the list that a new installation of the application tier includes the Oracle Fusion Middleware Stack (which includes Oracle WebLogic Server and the Web Tier), and the Oracle Application Server stack, which includes the forms and reports and the Oracle E-Business Suite application tier code.

A successful completion of application tier installation on node 2 configures the following services:

Root Service, comprising the Node Manager.
Web Administration Service, comprising WebLogic Administration Server and TNS Listener for FNDFS.
Web Entry Point Services, comprising the Oracle Process Notification Server (OPMN) and the Oracle HTTP Server (OHS).
Web Application Services, comprising the Managed Servers oacore, forms, oafm and form-c4ws.
Batch Processing Services, comprising the concurrent processing services, ICSM and JTF fullfillment server.
Other Services, comprising the Forms services and mobile web application services.

3.3 Execute adpreclone Utility on the Run and Patch File System

Note: Ensure that value of the AutoConfig variable " s_shared_file_system" is set to "true" ( without the quote) on the primary application tier node. This variable will be automatically set to "true" if the shared file system option was chosen during the Rapid Install.

The adpreclone utility shipped with Oracle E-Business Suite packages the required application tier components to a staging directory for subsequent clone and add node operations. You mustrun this utility before proceeding to Section 4 of this document.

The adpreclone utility requires the WebLogic Administration process to be running from the file system where the utility is run. This is required to package the Oracle Fusion Middleware components and its configuration. Perform the commands shown below on both the run and patch file systems:

On the run file system:

$ cd <inst-top-run-fs>/admin/scripts 
$ ./adadminsrvctl.sh start
$ ./adpreclone.pl appsTier

Once the utility completes, shut down the application tier processes:

$ ./adstpall.sh <apps-user-name>/<apps-password>

On the patch file system:

$ cd <inst-top-patch-fs>/admin/scripts 
$ ./adadminsrvctl.sh start forcepatchfs 
$ ./adpreclone.pl appsTier

Once the utility completes, shut down the application tier processes.

$ ./adstpall.sh <apps-user-name>/<apps-password>forcepatchfs

Follow section 4 after completing the installation of the database tier node and the primary application tier node.

Please note that an administrator can also use the Rapid Clone utlity to lay down the file system, configure the primary application tier node and subsequently add secondary application tier nodes using the share file system.

Note:Please note that an administrator can also use the Rapid Clone utlity to lay down the file system, configure the primary application tier node and subsequently add secondary application tier nodes using the share file system.

Section 4: Adding a Node to the Shared Application Tier File System

The tasks listed in this section assume that you have completed Section 3 of this document. The node to be added now will be known as the secondary application tier node. This node can be configured to run all services except for the Oracle WebLogic Administration Server

Note:

The fully qualified hostname of the application tier node to be added must be present in the sqlnet.ora file in the <Database_Oracle_ Home>/network/admin/<context-name> directory. (See tcp.invited_nodes parameter.)
The database and TNS listener must be running before the steps listed below are performed.
In a shared file system, User ID and group ID should be consistent across all nodes to avoid file access permission issues.
The same absolute path must be used for the shared file system mount points on each node.
Ensure that value of the AutoConfig variable "s_atName" is same across all the application tier node context files.
Ensure that value of the AutoConfig variable " s_shared_file_system" is set to "true" ( without the quote) on the primary application tier node. This variable will be automatically set to "true" if the shared file system option was chosen during the Rapid Install.
The oraInventory directory from the primary application tier and the oraInst.loc file must be accessible to all nodes sharing the application tier file system.
It is recommended to keep the Instance Top ( INST_TOP) on the shared file system for 1) Ease of maintenance 2) The number of application tier processes writing to this location is limited when compared with the previous releases.

The following example will be used to explain the provisioning process better.

Database tier is installed on: db.company.com
Primary Application tier is installed on: appstier1.company.com
Secondary Application tier to be added: appstier2.company.com
Directory location of the application tier file system on the primary Node: /u01/12.2
Primary Application tier run file system: /u01/12.2/fs1
Primary Application tier patch file system: /u01/12.2/fs2
OraInventory Directory: /u01/12.2/oraInventory

Before proceeding with the instructions given below, ensure that steps listed in section 3.3 Execute the Adpreclone Utility on the Run and Patch File System of this document is successfully completed.

4.1 Export the Required Application Tier File System From the Primary Node

The following application tier file systems need to be exported from the primary application tier:

/u01/12.2/fs1: The file system configured to be the run file system on install
/u01/12.2/fs2: The file system configured to be the patch file system on install
/u01/12.2/fs_ne: The file system configured to be the non-edition file system on install
/u01/12.2/oraInventory: The OraInventory directory

On a Linux system, execute the following commands as the root user to mount the application tier file system on to the secondary node.

Add the following lines to the /etc/exports file:
/u01/12.2/fs1 appstier2.company.com(rw,sync,no_root_squash) /u01/12.2/fs2 appstier2.company.com(rw,sync,no_root_squash) /u01/12.2/fs_ne appstier2.company.com(rw,sync,no_root_squash) /u01/12.2/oraInventory appstier2.company.com(rw,sync,no_root_squash)
Note: The export options described above may need to be adjusted according to the security requirements of your organization. Also, the available options may differ on other platforms.
Check whether the NFS daemons are running:
$ /sbin/service nfs status
If the NFS daemons are not running, execute the following command to start them:
$ /sbin/service nfs start
Once the NFS daemons are running, execute the following command to export the application tier file system:
$ $ /usr/sbin/exportfs -a
Ensure the application tier file systems are exported by executing the following command:
$ /usr/sbin/exportfs

4.2 Mount the Application Tier File System on the Secondary Node

The following application tier file system need to be mounted on the secondary application tier node from the primary node.

/u01/12.2/fs1: The file system configured to be the run file system on install
/u01/12.2/fs2: The file system configured to be the patch file system on install
/u01/12.2/fs_ne: The file system configured to be the non-edition file system on install
/u01/12.2/oraInventory: The OraInventory directory

Check whether the NFS daemons are running:
$ /sbin/service nfs status
If the NFS daemons are not running, execute the following command to start them:
$ /sbin/service nfs start
Create directories as follows:
$ /bin/mkdir -p /u01/12.2/fs1$ /bin/mkdir -p /u01/12.2/fs2 $ /bin/mkdir -p /u01/12.2/fs_ne$ /bin/mkdir -p /u01/12.2/oraInventory
Change the ownership and group permissions of these directories to be the same as that from the primary application tier node. For example if oracle is the owner of the file system and is in the group dba, you need to execute the commands shown below:
$ /bin/chown -R oracle /u01/12.2/fs1
$ /bin/chown -R oracle /u01/12.2/fs2
$ /bin/chown -R oracle /u01/12.2/fs_ne
$ /bin/chown -R oracle /u01/12.2/oraInventory
$ /bin/chgrp -R dba /u01/12.2/fs1
$ /bin/chgrp -R dba /u01/12.2/fs2
$ /bin/chgrp -R dba /u01/12.2/fs_ne
$ /bin/chgrp -R dba oraInventory
Use the following commands to mount the application tier file system from the primary node to the secondary node:
$ cd /u01/12.2/fs1$ /bin/mount -t nfs -o rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp appstier1.company.com:/u01/12.2/fs1 .

$ cd /u01/12.2/fs2
$ /bin/mount -t nfs -o rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp appstier1.company.com:/u01/12.2/fs2 .

$ cd /u01/12.2/fs_ne
$ /bin/mount -t nfs -o rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp appstier1.company.com:/u01/12.2/fs_ne .

$ cd /u01/12.2/oraInventory$ /bin/mount -t nfs -o rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp appstier1.company.com:/u01/12.2/oraInventory .
Note: Be sure to include the space and period at the end of each mount command, the period denoting that the current directory is to be used as the mount point.

Refer to Appendix A: Mount Options For Network File Systems for the mount option to be used for mounting the application tier file system.
Prepare to add file system information to the /etc/fstab file, so that the primary application tier file system will be automatically mounted on reboot:
$ cd /etc$ vi fstab
In vi (or an equivalent editor), add lines as per the following example:
appstier1.company.com:/u01/12.2/fs1 /u01/12.2/fs1 nfs rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp 0 0
appstier1.company.com:/u01/12.2/fs2 /u01/12.2/fs2 nfs rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp 0 0

appstier1.company.com:/u01/12.2/fs_ne /u01/12.2/fs_ne nfs rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp 0 0
appstier1.company.com:/u01/12.2/oraInventory /u01/12.2/oraInventory nfs rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp 0 0

4.3 Add the Secondary Application Tier Node to the Farm

The primary decision that an administrator need to make before proceeding with the steps given below is to decide what services are going to be configured on the secondary node. The new node that you are planning to add can run any service except for WebLogic Administration Server, which is only configured on the primary application tier node. Follow the steps given below to add a node.

4.3.1 Prepare the PairsFile for Configuring the Run File System

DELTA 6 Code Level Flow

A sample pairsfile for the run file system is instantiated into the relevant instance home on the primary application tier node. The name of the file is<SID>_<primary_node_name>_<file_edition_type>.txt, located in the <INST_TOP>/appl/admin/ directory. For a configuration with an instance name of VIS, the pairsfile will be/u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1_run.txt.

Carry out the instructions below to prepare the pairsfile for configuring the run file system.

Create the required directories, then copy the pairsfile into a directory of your choice on the secondary application tier node. For example:
$ mkdir -p /u01/12.2/pairsfiles/run
$ cd /u01/12.2/pairsfile/run$ cp /u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1_run.txt myrunpairsfile.txt
Make necessary modifications to the pairsfile. Some of the inputs required for the Add Node API are automatically filled in. The sections that you need to fill in are the following.

[Instance Specific] - This is instance specific information for the node you are going to add. Refer to the source context file for reference.

[Services]

4.3.2 Configure the Run File System on the Secondary Node

Carry out the instructions below to configure the run file system on the secondary node.

Ensure the correct perl utility is in the $PATH. You must use the perl utility installed in the Fusion Middleware Oracle Home.

For example:
$ export PATH=/u01/12.2/fs1/FMW_Home/webtier/perl/bin:$PATH
Ensure the WebLogic Administration Server from the run file system is running on the primary application tier node.
Execute the Clone Context Utility to configure the run file system. For example:
$ cd /u01/12.2/fs1/EBSapps/comn/clone/bin $ /u01/12.2/fs1/FMW_Home/webtier/perl/bin/perl ./adclonectx.pl \ addnode contextfile=/u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.xml \ pairsfile=/u01/12.2/pairsfile/run/myrunpairsfile.txt \ outfile=/u01/12.2/fs1/inst/apps/VIS_appstier2/appl/admin/VIS_appstier2.xml
Review the EBSProvisioner.log file created in the current directory to ensure the add node program completed without any errors.

4.3.3 Prepare the PairsFile for Configuring the Patch File System

Carry out the instructions given below to prepare the pair files for configuring the patch file system.

A sample pairsfile each for the patch file system is instantiated into the respective instance home on the primary application tier node. The file is called<SID>_<primary_node_name>_<file_edition_type>.txt, and located in the <inst_top>/appl/admin/ directory. For a configuration with an instance name of VIS, the pairsfile will be /u01/12.2/fs2/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1_patch.txt.
Create the required directories and copy the pairsfile into a directory of your choice on the secondary application tier node. For example:
$ /bin/mkdir -p /u01/12.2/pairsfiles/patch
$ cd /u01/12.2/pairsfile/patch$ /bin/cp /u01/12.2/fs2/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1_patch.txt mypatchpairsfile.txt
Make necessary modifications to the pairsfile. Some of the inputs required for the Add Node API are automatically filled in. The sections that you need to fill in are the following:

[Instance Specific] - This is instance specific information for the node you are going to add. Refer to the source context file for more information.

[Services]

4.3.4 Configure the Patch File System on the Secondary Node

Carry out the instructions given below to configure the patch file system on the secondary node:

Ensure the correct perl utility is in the $PATH. You must use the perl utility installed in the Fusion Middleware Oracle Home.

For example:
$ export PATH=/u01/12.2/fs2/FMW_Home/webtier/perl/bin:$PATH
Ensure the WebLogic Administration Server from the patch file system is running on the primary application tier node.
Execute the Clone Context Utility to configure the patch file system. For example:
$ cd /u01/12.2/fs2/EBSapps/comn/clone/bin $ /u01/12.2/fs2/FMW_Home/webtier/perl/bin/perl ./adclonectx.pl \ addnode contextfile=/u01/12.2/fs2/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.xml \ pairsfile=/u01/12.2/pairsfile/patch/mypatchpairsfile.txt \ outfile=/u01/12.2/fs2/inst/apps/VIS_appstier2/appl/admin/VIS_appstier2.xml
Review the EBSProvisioner.log file created in the current directory to ensure the add node program completed without any errors.
Shutdown any application tier processes that may have been started while configuring the patch file system.

DELTA 7 Code Level Flow

The AD/TXK D7 patch introduce a new flow that adds both the run and patch edition file system with a single command. The steps given below configures both Run and Patch edition file system for a new node that is going to be added to the farm.

1. Ensure the correct perl utility is in the $PATH. You must use the perl utility installed in the Fusion Middleware Oracle Home.

For example:

$ export PATH=/u01/12.2/fs1/FMW_Home/webtier/perl/bin:$PATH

2. Ensure the WebLogic Administration Server is running from both run and Patch file system on the primary application tier node.

3. A sample pairsfile for the run/patch file system is instantiated into the instance home on the primary application tier node. The file is called <SID>_<primary_node_name>_.txt, and located in the <inst_top>/appl/admin/ directory. For a configuration with an instance name of VIS, the pairsfile will be /u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.txt.

4.Create the required directories and copy the pairsfile into a directory of your choice on the secondary application tier node. For example:

$ /bin/mkdir -p /u01/12.2/pairsfiles
$ cd /u01/12.2/pairsfile
$ /bin/cp /u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.txt mypairsfile.txt

5. Execute adclonectx utility to configure both run and Patch file system

$ cd /u01/12.2/fs1/EBSapps/comn/clone/bin
$ /u01/12.2/fs1/FMW_Home/webtier/perl/bin/perl ./adclonectx.pl \
addnode contextfile=/u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.xml \ 
pairsfile=/u01/12.2/pairsfile/mypairsfile.txt \
dualfs=yes

4. Review the log files displayed by the add node utility to ensure that the add node operation has gone through successfully.

4.3.5 Register the new Topology [Required]

Follow the instructions given in section 5.3.2.4-5.3.2.7 ( Register the new topology from the newly added application tier node) of My Oracle Support Note Knowledge document Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1) to register the new topology after adding the nodes.

4.3.6: SSH Connectivity Requirements for Online Patching (Required)

The 12.2 online patching tool adop requires ssh connectivity between the primary application tier node often called as the master node configured in the intranet with other application tier nodes configured in both the Intranet and in the DMZ. This connectivity is required for the remote invocation of the patching procedures on all the nodes. See Set up Secure Shell on Application tier Nodes in the Oracle E-Business Suite Maintenance Guide for more information.

Section 5: References

Rapid Clone
Rapid Clone automates and simplifies the process of cloning an Oracle E-Business Suite Release 12.2 system. For details, refer document 406982.1=""to Oracle E-Business Suite Setup Guide.
AutoConfig
AutoConfig is a tool to configure an Oracle E-Business Suite Release 12.2 instance. For details, refer to Oracle E-Business Suite Setup Guide.

Oracle Fusion Middleware on Shared Storage : Best Practices

Oracle E-Business Suite on Oracle Engineered Systems

Appendix A: Mount Options For Network File Systems

The recommendation given below are based on the testing performed by Oracle Development on commodity hardware running Linux operating system. The parameters listed below may not apply to Oracle Engineered systems. Please refer to Oracle E-Business Suite on Oracle Engineered Systems for more details on the mount options to be used.These parameters also may need to be tuned depending on various attributes related to network setup between the application tier machines , shared storage used, load on the storage server etc. Please contact your storage vendor to tune the NFS parameters for best throughput.

Platform	NFS Mount Options for Application Tier	NFS Mount Options for Database Oracle Home	NFS Mount Options for Database Files
Linux	`rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,nfsvers=3,tcp`	`rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,nfsvers=3,tcp`	`rw,nointr,bg,hard,timeo=600,wsize=32768,rsize=32768,nfsvers=3,tcp`
Solaris	`rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,vers=3,proto=tcp`	`rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,vers=3,proto=tcp`	`rw,nointr,bg,hard,timeo=600,wsize=32768,rsize=32768,vers=3,proto=tcp`
IBM AIX	`rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,vers=3,proto=tcp`	`rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,vers=3,proto=tcp`	`rw,nointr,bg,hard,timeo=600,wsize=32768,rsize=32768,vers=3,proto=tcp`
HP Itanium	`rw,nointr,bg,hard,timeo=600,wsize=65536,rsize=65536,vers=3,proto=tcp`	`rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,vers=3,proto=tcp`	`rw,nointr,bg,hard,timeo=600,wsize=32768,rsize=32768,vers=3,proto=tcp`

please note that the nfs mount options " intr" and "nointr" mount options are deprecated with Oracle Linux re deprecated in Oracle Unbreakable Enterprise Linux and Oracle Linux kernels, 2.6.32 and later.

Additional Setup Requirements for NFS File Systems

Appendix B: Known Issues

Date	Known Issue	Resolution	Fixed In
November 11, 2013	Oracle E-Business Suite Domain creation fails on certain NFS storage with weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information.	The workaround is to ensure that the storage is mounted with "noacl" NFS mount option.

Change Log

Date	Description
MAY 21 , 2016	Updates for AD/TXK D7 and OCFS2 file system
FEB 23, 2015	NFS mount options for application tier file system updated ( removed nolock, intr changed to nointr , rsize and wsize changed to 65536) , Added additional shared storage requirements.
AUG 25, 2014	Removed acregmax,acregmin NFS parameters from the mount options for better peformance.
JUL 24, 2014	Note updated based on suggestions from remarks and bugs.
FEB 21, 2014	Note section updated to highlight shared file system variable need to be set to true
NOV 25, 2013	Updates in sections 4.3.1, 4.3.3, 4.3.4, and 4.3.5.
AUG 14, 2013	Edited in readiness for publication.
MAR 13, 2012	Initial document creation.

posted on 2016-06-08 11:33 王小航阅读(1530) 评论(0) 编辑收藏举报

刷新页面返回顶部

王小航