Chapter 11.27Setting Shell Limits for the Oracle UserMost shells like Bash provide control over various resources like the maximum allowable number ofopen file descriptors or the maximum number of processes available to a user.To see all shell limits, run:ulimit -aFor more information on ulimit for the Bash shell, see man bash and search for ulimit.NoteOn some Linux systems setting "hard" and "soft" limits in the following examples mightnot work properly when you log in as user oracle via SSH. It might work if you log in asroot and su to oracle. If you have this problem try to set UsePrivilegeSeparationto "no" in /etc/ssh/sshd_config and restart the SSH daemon by executing servicesshd restart. The privilege separation does not work properly with PAM on someLinux systems. Make sure to talk to the people in charge of security before disabling theSSH security feature "Privilege Separation".11.1. Limiting Maximum Number of Open File Descriptorsfor the Oracle UserAfter /proc/sys/fs/file-max has been changed, see Chapter 9, Setting File Handles, there isstill a per user limit of maximum open file descriptors:$ su - oracle$ ulimit -n1024$To change this limit, edit the /etc/security/limits.conf file as root and make the followingchanges or add the following lines, respectively:oracle soft nofile 4096oracle hard nofile 63536The "soft limit" in the first line defines the number of file handles or open files that the Oracle user willhave after they log in. If the Oracle user gets error messages about running out of file handles, thenthe Oracle user can increase the number of file handles like in this example up to 63536 ("hard limit")by executing the following command:ulimit -n 63536You can set the "soft" and "hard" limits higher if necessary.NoteIt is not recommend to set the "hard" limit for nofile for the oracle user equal to /proc/sys/fs/file-max. If you do that and the user uses up all the file handles, then the
