oracle安装参数,Oracle安装内核参数设置

oracle support 说明：

Modify your kernel settings in /etc/sysctl.conf as follows. If the current value for any parameter is higher than the value listed in this table, do not change the value of that parameter. Range values (such as net.ipv4.ip_local_port_range) must match exactly.

kernel.shmall = half the size of physical memory in pages (If the server supports multiple databases, or uses a large SGA, then set this parameter to a value that is equal to the total amount of shared memory, in 4K pages, that the system can use at one time.)

kernel.shmmax = 1/2 of physical RAM in bytes. This would be the value 2147483648 for a system with 4Gb of physical RAM. (refer Note 567506.1 for additional information about configuring shmmax.)

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

fs.file-max = 512 x processes (for example 6815744 for 13312 processes)

fs.aio-max-nr = 1048576

net.ipv4.ip_local_port_range = 9000 65500

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048576

vm.hugetlb_shm_group =

To activate these new settings into the running kernel space, run the “sysctl –p” command as root.

Set Shell Limits for the oracle User. Assuming that the “oracle” Unix user will perform the installation, do the following:

a) Add the following settings to /etc/security/limits.conf

oracle soft nproc 2047

oracle hard nproc 16384

oracle soft nofile 1024

oracle hard nofile 65536

oracle soft stack 10240

oracle hard stack 10240

b) Add or edit the following line in the /etc/pam.d/xdm file, if it does not already exist:

session required pam_limits.so

c) Add or edit the following line in the /etc/pam.d/su file, if it does not already exist:

session required pam_limits.so

The gcc and g++ RPM items above will ensure that the correct gcc / g++ versions are installed. It is also required that you ensure that these correct gcc / g++ versions are active, and in-use. Ensure that the commands “gcc –version” and “g++ –version” each return “4.3.x”.

The hostname command should return the fully qualified hostname as shown

below:

% hostname -f

hostname.domainname

If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.

The oracle account used to install Oracle Database 12.1, should not have the Oracle install related variables set by default. For example setting ORACLE_HOME, PATH, LD_LIBRARY_PATH to include Oracle binaries in .profile, .login file and /etc/profile.d should be completely avoided.

a.) Setting ORACLE_HOME) is recommended, since it eases a few prompts in the OUI runInstaller tool.

b.) following the successful install, it is recommended to set PATH to include PATH string.

Log in as Oracle user and start the installation as follows:

./runInstaller

a.) it is best practice not to use any form of “su” to start the runInstaller, in order to avoid potential display-related problems.

b.) When performing the Oracle Database 12.1 installation, make sure to use the “runInstaller” version that comes with Oracle Database 12.1 software.

c.) When performing any subsequent Oracle Database 12.1 patchset, make sure to use the “runInstaller” version that comes with the patchset.