No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

KunLun Mission Critical Server Oracle Database Oracle 12c R1 (RAC) Best Practice 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Modifying System Parameters

Modifying System Parameters

Perform the following operations on each database node as user root.

Procedure

  1. Set the system user login limit parameter.

    [root@dbn01 ~]# vi /etc/pam.d/login  
    session required pam_limits.so  #Add the line to the end of the configuration file.

    After the parameter is set, the user login process loads the pam_limits.so module and sets the login limits according to the /etc/security/limits.conf file.

  2. Modify the /etc/systemd/logind.conf file and add RemoveIPC=no to the file. If the logind.conf file does not exist on the OS, skip this section.

  3. Set SELINUX to disabled.

    [root@dbn01~]# vi /etc/selinux/config   
    # This file controls the state of SELinux on the system.  
    # SELINUX= can take one of these three values:  
    #     enforcing - SELinux security policy is enforced.  
    #     permissive - SELinux prints warnings instead of enforcing.  
    #     disabled - No SELinux policy is loaded.  
    SELINUX=disabled 
    # SELINUXTYPE= can take one of these two values:  
    #     targeted - Targeted processes are protected,  
    #     mls - Multi Level Security protection.  
    SELINUXTYPE=targeted     

  4. Configure the etc/security/limits.conf file.

    NOTE:

    Add new parameters to the end of the configuration file instead of the middle to prevent the parameters from being overwritten.

    The value of memlock is 90% of the physical memory.

    • If the OS is RHEL 6, add the following content:
      [root@dbn01 ~]# vi /etc/security/limits.conf  
      #ORACLE SETTING  
      grid                 soft    nproc   65536  
      grid                 hard    nproc   65536  
      grid                 soft    nofile  65536  
      grid                 hard    nofile  65536  
      oracle               soft    nproc   65536  
      oracle               hard    nproc   65536  
      oracle               soft    nofile  65536  
      oracle               hard    nofile  65536
      oracle               soft    memlock 1425011166
      oracle               hard    memlock 1425011166
    • If the database node OS is RHEL 7, add the following content:
      [root@dbn01 ~]# vi /etc/security/limits.conf  
      #ORACLE SETTING  
      grid                 soft    nproc   65536  
      grid                 hard    nproc   65536  
      grid                 soft    nofile  65536  
      grid                 hard    nofile  65536  
      oracle               soft    nproc   65536  
      oracle               hard    nproc   65536  
      oracle               soft    nofile  65536  
      oracle               hard    nofile  65536 
      grid                 soft    stack  65536 
      oracle               soft    stack  65536    
      oracle               soft    memlock 1425011166
      oracle               hard    memlock 1425011166

  5. Configure the /etc/sysconfig/network file.

    [root@dbn01~]# vi /etc/sysconfig/network
    NOZEROCONF=yes

  6. Configure the /etc/sysctl.conf file.

    NOTE:
    • Add new parameters to the end of the configuration file instead of the middle to prevent the parameters from being overwritten.
    • kernel.shmmax: The value is calculated based on the physical memory capacity. In this example, the physical memory of the node is 512 GB. It is recommended that the value of kernel.shmmax be 70% of the physical memory of the node. The value unit is byte. The value in this example is calculated as follows: 512 x 70% x 1024 x 1024 x 1024 = 384829069721.6 (rounded up to 384829069722).
    • kernel.shmall: calculated based on SGA/PAGE_SIZE.
    • kernel.sem: If the number of processes supported by a single database exceeds 12000, set this parameter based on the actual situation.
    [root@dbn01~]# vi /etc/sysctl.conf  
    #ORACLE SETTING  
    kernel.shmall = 4294967296  
    kernel.shmmax = 384829069722  
    kernel.shmmni = 4096  
    kernel.sem = 12000 1536000 100 128 
    fs.file-max = 6815744  
    fs.aio-max-nr = 3145728 
    net.ipv4.ip_local_port_range = 9000 65500  
    net.ipv4.ipfrag_high_thresh = 16777216 
    net.ipv4.ipfrag_low_thresh = 15728640  
    net.core.rmem_default = 262144  
    net.core.rmem_max = 4194304   
    net.core.wmem_default = 262144   
    net.core.wmem_max = 1048576   
    vm.min_free_kbytes= 1048576

  7. Run the following command as user root to activate the newly configured system parameters:

    [root@dbn01~]# sysctl -p

Download
Updated: 2019-02-01

Document ID: EDOC1100053123

Views: 13902

Downloads: 14

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next