It is important to perform a set of tasks on each computer or server before configuring the enterprise deployment topology. This involves verifying the minimum hardware and operating system requirements for each host, configuring operating system users and groups, enabling Unicode support, mounting the required shared storage systems to the host and enabling the required virtual IP addresses on each host.
This chapter describes the tasks you must perform from each computer or server that will be hosting the enterprise deployment.
After procuring the required hardware for the enterprise deployment, it is important to ensure that each host computer meets the minimum system requirements.
After you have procured the required hardware for the enterprise deployment, log in to each host computer and verify the system requirements listed in Hardware and Software Requirements for the Enterprise Deployment Topology.
If you are deploying to a virtual server environment, such as Oracle Exalogic, ensure that each of the virtual servers meets the minimum requirements.
Ensure that you have sufficient local disk storage and shared storage configured as described in Preparing the File System for an Enterprise Deployment.
Allow sufficient swap and temporary space; specifically:
Swap Space–The system must have at least 500 MB.
Temporary Space–There must be a minimum of 500 MB of free space in
You can review the typical Linux operating system settings for an enterprise deployment in this section.
To ensure the host computers meet the minimum operating system requirements, be sure you have installed a certified operating system and that you have applied all the necessary patches for the operating system.
In addition, review the following sections for typical Linux operating system settings for an enterprise deployment.
The kernel-parameter and shell-limit values shown below are recommended values only. Oracle recommends that you tune these values to optimize the performance of the system. See your operating system documentation for more information about tuning kernel parameters.
Kernel parameters must be set to a minimum of those in Table 8-1 on all nodes in the topology.
The values in the following table are the current Linux recommendations. For the latest recommendations for Linux and other operating systems, see Oracle Fusion Middleware System Requirements and Specifications.
If you are deploying a database onto the host, you might need to modify additional kernel parameters. Refer to 12c (220.127.116.11) Configuring Kernel Parameters in Oracle Grid Infrastructure Installation Guide for Linux.
Table 8-1 UNIX Kernel Parameters
256 32000 100 142
To set these parameters:
rootand add or amend the entries in the file
On UNIX operating systems, the
Open File Limit is an important system setting, which can affect the overall performance of the software running on the host computer.
For guidance on setting the
Open File Limit for an Oracle Fusion Middleware enterprise deployment, see Host Computer Hardware Requirements.
The following examples are for Linux operating systems. Consult your operating system documentation to determine the commands to be used on your system.
For more information, see the following sections.
You can see how many files are open with the following command:
/usr/sbin/lsof | wc -l
To check your open file limits, use the following commands.
To change the Open File Limit values:
rootuser and edit the following file:
limits.conffile. (The values shown here are for example only):
* soft nofile 4096 * hard nofile 65536 * soft nproc 2047 * hard nproc 16384
nofiles values represent the open file limit; the
nproc values represent the number of processes limit.
Before you begin the installation of the Oracle software, ensure that the IP address, fully qualified host name, and the short name of the host are all registered with your DNS server. Alternatively, you can use the local
hosts file and add an entry similar to the following:
IP_Address Fully_Qualified_Name Short_Name
10.229.188.205 host1.example.com host1
The users and groups to be defined on each of the computers that host the enterprise deployment are listed in this section.
You must create the following groups on each node.
You must create the following user on each node.
nobody–An unprivileged user.
oracle–The owner of the Oracle software. You may use a different name. The primary group for this account must be
oinstall. The account must also be in the
oinstall must have write privileges to all the file systems on shared and local storage that are used by the Oracle software.
Each group must have the same Group ID on every node.
Each user must have the same User ID on every node.
It is recommended to enable Unicode support in your operating system so as to allow processing of characters in Unicode.
Your operating system configuration can influence the behavior of characters supported by Oracle Fusion Middleware products.
On UNIX operating systems, Oracle highly recommends that you enable Unicode support by setting the
LC_ALL environment variables to a locale with the UTF-8 character set. This enables the operating system to process any character in Unicode. Oracle Business Intelligence technologies, for example, are based on Unicode.
If the operating system is configured to use a non-UTF-8 encoding, Oracle Business Intelligence components may function in an unexpected way. For example, a non-ASCII file name might make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.
It is important to understand how to mount the shared storage to all the servers that require access.
The shared storage configured, as described in Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment, must be available on the hosts that use it.
In an enterprise deployment, it is assumed that you have a hardware storage filer, which is available and connected to each of the host computers you have procured for the deployment.
You must mount the shared storage to all servers that require access.
Each host must have appropriate privileges set within the Network Attached Storage (NAS) or Storage Area Network (SAN) so that it can write to the shared storage.
Follow the best practices of your organization for mounting shared storage. This section provides an example of how to do this on Linux using NFS storage.
You must create and mount shared storage locations so that BIHOST1 and BIHOST2 can see the same location if it is a binary installation in two separate volumes.
For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
You use the following command to mount shared storage from a NAS storage device to a Linux host. If you are using a different type of storage device or operating system, refer to your manufacturer documentation for information about how to do this.
The user account used to create a shared storage file system owns and has read, write, and execute privileges for those files. Other users in the operating system group can read and execute the files, but they do not have write privileges.
For more information about installation and configuration privileges, see Selecting an Installation User in the Oracle Fusion Middleware Installation Planning Guide.
In the following example,
nasfiler represents the shared storage filer. Also note that these are examples only. Typically, the mounting of these shared storage locations should be done using the
/etc/fstabs file on UNIX systems, so that the mounting of these devices survives a reboot. Refer to your operating system documentation for more information.
Create the mount directories on BIHOST1, as described in Summary of the Shared Storage Volumes in an Enterprise Deployment, and then mount the shared storage. For example:
mount -t nfs nasfiler:VOL1/oracle/products/ /u01/oracle/products/
Repeat the procedure on BIHOST2 using VOL2.
Validating the Shared Storage Configuration
Ensure that you can read and write files to the newly mounted directories by creating a test file in the shared storage location you just configured.
$ cd newly mounted directory $ touch testfile
Verify that the owner and permissions are correct:
$ ls -l testfile
Then remove the file:
$ rm testfile
The shared storage can be a NAS or SAN device. The following example illustrates creating storage for a NAS device from BIHOST1. The options may differ depending on the specific storage device.
mount -t nfs -o rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768 nasfiler:VOL1/Oracle/u01/oracle
Contact your storage vendor and machine administrator to learn about the appropriate options for your environment.
You must enable the required virtual IP addresses on each host in order to prepare the host for the enterprise deployment. The procedure varies, depending on whether you are using Oracle Enterprise Linux 5 or Oracle Enterprise Linux 6.
Oracle Enterprise Linux 5
To prepare each host for the enterprise deployment, you must enable the virtual IP (VIP) addresses described in Reserving the Required IP Addresses for an Enterprise Deployment.
It is assumed that you have already reserved the VIP addresses and host names and that they have been enabled by your network administrator. You can then enable the VIPs on the appropriate host.
Note that the virtual IP addresses used for the enterprise topology are not persisted because they are managed by Whole Server Migration (for selected Managed Servers and clusters) or by manual failover (for the Administration Server).
To enable the VIP addresses on each host, run the following commands as
/sbin/ifconfig interface:index IPAddress netmask netmask /sbin/arping -q -U -c 3 -I interface IPAddress
/sbin/ifconfig eth0:1 18.104.22.168 netmask 255.255.255.0
Enable your network to register the new location of the virtual IP address:
/sbin/arping -q -U -c 3 -I eth0 22.214.171.124
Validate that the address is available by using the
ping command from another node, for example:
Oracle Enterprise Linux 6 or Later
Starting with Oracle Enterprise Linux 6, the "
ifconfig" command is deprecated and is replaced with the "
ip addr show dev bond0
2: bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:21:f6:03:85:9f brd ff:ff:ff:ff:ff:ff int 192.168.20.1/20 brd 10.248.11.255 scope global bond0
ip addr add 192.168.20.3/20 dev bond0:1
arping -b -A -c 3 -I bond0 192.168.20.3
Note:Due to a known issue in the
ifconfigutility, during server migration, all VIPs are dropped from the network interface on the machine the WebLogic Managed Server is migrated from. This happens when the VIP is enabled on
:0of the network interface. To workaround the issue, enable the VIPs on the network interface starting with