Installing Oracle Linux - Expert Consolidation in Oracle Database 12c - page 167

Using the values from Tables 5-3 and 5-4 , the resulting /etc/sysctl.conf file contains these lines:
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 6815744
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_max = 1048576
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65500
You do not need to worry about these though. The Oracle Universal Installer provides a “fixup” option during
the installation which can modify the kernel parameters to set the required minimum values. In addition, the Oracle
server preinstall RPM ensures that you meet these minimum requirements. You can read more about the preinstall-
RPM later in this chapter.
The Oracle mount points
The mount points and file systems suggested for use with the Oracle binaries have been discussed in the section
“Considerations for the Oracle mount point”. Assuming that the storage has been formatted during the installation,
the remaining work is simple: just update the file system table in /etc/fstab with a mount point for the Oracle
software and you are done. Most often, the Oracle binaries are installed following the Optimal Flexible
Architecture-OFA.
The starting point for mounting the file systems for use with Oracle usually is the /u01 directory and the hierarchy
beneath. Alternatively you could use the top-level directory defined in your standards document. The next few
paragraphs follow the OFA recommendation.
First, you need to consider the location of the Oracle inventory. The inventory is often owned by the oracle
account but more importantly is owned by the operating system group oinstall . This ensures that in the case of
separation of duties other operating system accounts have write permissions to the global inventory location. It is
also the reason it is so important to define oinstall as the primary group for the oracle and grid user. In many
deployments you will find the Oracle inventory in /u01/app/oraInventory , which is also the default.
Before discussing the installation location of Grid Infrastructure it is important to cover the ORACLE_BASE.
For the Grid Infrastructure installation, the Oracle base signifies the location where certain diagnostic and other
important log files are stored. From a database perspective, the most important subdirectory is the diagnostic
destination which has been introduced with Oracle 11.
An important restriction exists for the installation of the Grid Infrastructure for a cluster: the GRID_HOME must
not be in the path of any ORACLE_BASE on your system.
The default location for Grid Infrastructure in a cluster configuration is /u01/app/12.1.0/grid, but in the author's
opinion you should use one more digit to indicate the version number, i.e. /u01/app/12.1.0.1/grid instead. This will
make it easier during patching to identify a software home. Remember that Oracle introduced full releases with the
first patch set to 11g Release 2, which are out-of-place upgrades.
To sum it up the following directories are needed for an OFA-compliant installation. You can use these as mount
points for the logical volumes defined earlier during the installation:
# mkdir -p /u01/app/oraInventory # Path for the inventory
# mkdir -p /u01/app/oracle # ORACLE_BASE for the database owner
# mkdir -p /u01/app/grid # ORACLE_BASE for the grid owner