During installation the user that is installing the software should have the

During installation the user that is installing the

This preview shows page 96 - 99 out of 228 pages.

During installation, the user that is installing the software should have the OINSTALL group as its primary group, and it must be a member of the operating system groups appropriate for your installation. For example: # /usr/sbin/usermod -g oinstall -G dba,asmdba,backupdba,dgdba,kmdba,racdba[,oper] oracle Creating Operating System Oracle Installation User Accounts 5-14 Oracle Database Installation Guide
Image of page 96
5.4.5 Checking Resource Limits for Oracle Software Installation Users For each installation software owner user account, check the resource limits for installation. On Oracle Linux systems, Oracle recommends that you install Oracle Preinstallation RPMs to meet preinstallation requirements like configuring your operating system to set the resource limits in the 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: 1. Log in as an installation owner. 2. Check the soft and hard limits for the file descriptor setting. Ensure that the result is in the recommended range. For example: $ ulimit -Sn 1024 $ ulimit -Hn 65536 3. Check the soft and hard limits for the number of processes available to a user. Ensure that the result is in the recommended range. For example: $ ulimit -Su 2047 $ ulimit -Hu 16384 4. Check the soft limit for the stack setting. Ensure that the result is in the recommended range. For example: Creating Operating System Oracle Installation User Accounts Configuring Users, Groups and Environments for Oracle Grid Infrastructure and Oracle Database 5-15
Image of page 97
$ ulimit -Ss 10240 $ ulimit -Hs 32768 5. Repeat this procedure for each Oracle software installation owner. 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.
Image of page 98
Image of page 99

You've reached the end of your free preview.

Want to read all 228 pages?

  • Winter '15
  • Zaki
  • Oracle Database, Oracle Corporation

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture