在安装RAC时需要配置的几个kernel参数

--在安装RAC时需要配置的几个kernel参数
etl@Linux[/home/etl]cat /etc/sysctl.conf
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.

# Controls IP packet forwarding
net.ipv4.ip_forward = 0

# Controls source route verification
net.ipv4.conf.default.rp_filter = 1

# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0

# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 0

# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1

kernel.shmmax = 2368709120
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
--EOF---

--相关的解释如下:
/proc/sys/kernel/shmall 共享内存总页数系统限制
This file contains the system-wide limit on the total number of pages of System V shared memory.

/proc/sys/kernel/shmmax 最大共享内存段运行时限制
This file can be used to query and set the run time limit on the maximum (System V IPC) shared memory segment size
that can be created. Shared memory segments up to 1Gb are now supported in the kernel. This value defaults to
SHMMAX.

/proc/sys/kernel/shmmni 系统范围内共享内存段的最大数量
(available in Linux 2.4 and onwards) This file specifies the system-wide maximum number of System V shared memory
segments that can be created.

/proc/sys/kernel/sem (since Linux 2.4)
This file contains 4 numbers defining limits for System V IPC semaphores. These fields are, in order:
单个信号量集的最大信号量数:
SEMMSL The maximum semaphores per semaphore set.
系统所有信号量集总信号量数:
SEMMNS A system-wide limit on the number of semaphores in all semaphore sets.
单个信号量调用最大操作数量:
SEMOPM The maximum number of operations that may be specified in a semop(2) call.
系统信号量标识最大数量:
SEMMNI A system-wide limit on the maximum number of semaphore identifiers.

[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/23937368/viewspace-1044395/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/23937368/viewspace-1044395/