Checking Resource Limits for Oracle Software Installation Users
For each installation software owner user account, check the resource limits for installation.
limits.conf
file. Oracle Preinstallation RPM only configures the limits.conf
file for the oracle
user. If you are implementing Oracle Grid Infrastructure job role separation, then copy the values from the oracle
user to the grid
user in the limits.conf
file.
Use the following ranges as guidelines for resource allocation to Oracle installation owners:
Table 5-1 Installation Owner Resource Limit Recommended Ranges
Resource Shell Limit | Resource | Soft Limit | Hard Limit |
---|---|---|---|
Open file descriptors |
nofile |
at least 1024 |
at least 65536 |
Number of processes available to a single user |
nproc |
at least 2047 |
at least 16384 |
Size of the stack segment of the process |
stack |
at least 10240 KB |
at least 10240 KB, and at most 32768 KB |
Maximum locked memory limit | memlock | at least 90 percent of the current RAM when HugePages memory is enabled and at least 3145728 KB (3 GB) when HugePages memory is disabled | at least 90 percent of the current RAM when HugePages memory is enabled and at least 3145728 KB (3 GB) when HugePages memory is disabled |
To check resource limits:
If necessary, update the resource limits in the /etc/security/limits.conf
configuration file for the installation owner. However, the configuration file may be distribution specific. Contact your system administrator for distribution specific configuration file information.
Note:
If you make changes to an Oracle installation user account and that user account is logged in, then changes to the limits.conf
file do not take effect until you log these users out and log them back in. You must do this before you use these accounts for installation.