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

FusionCube DB 3.1 Database Best Practice 03 (Oracle RAC 11g R2)

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 all database nodes as user root.
  • Add new parameters to the end of the configuration file to prevent the parameters from being overwritten.

Procedure

  1. Set the system user login limit parameter.

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

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

  2. Set SELINUX to disabled.

    NOTE:

    This parameter needs to be modified only when a database node is manually installed.

    [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     

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

    NOTE:

    Add the following content to the end of the file. Do not add the content to the middle to prevent the values of the parameters at the end from overwriting the new values.

    • If the database node OS is Red Hat Enterprise Linux 6 or Oracle Linux 6, add the following content:
      [root@dbn01 ~]# vi /etc/security/limits.conf 
      root  soft  nofile 65536 
      root  hard  nofile 65536 
      * soft memlockunlimited 
      * hard memlockunlimited 
      #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     
    • If the database node OS is Red Hat Enterprise Linux 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    
      

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

    NOTE:
    • Add the following content to the end of the file. Do not add the content to the middle to prevent the values of the parameters at the end from overwriting the new values.
    • kernel.shmmax: The value is calculated based on the actual physical memory. In this example, the value is calculated based on the physical memory 512 GB of the node. It is recommended that the value of kernel.shmmax be 70% of the physical memory of the node. The 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.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     

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

    [root@dbn01~]# sysctl -p

Translation
Download
Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 32018

Downloads: 42

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