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).
Configuring the Cluster Installation Directory

Configuring the Cluster Installation Directory

The Oracle RAC installation directory is /u01, which needs to be manually mounted.

NOTE:

Perform the following operations on all database nodes.

Procedure

  1. Run the lsblk command and ensure that there is at least 200 GB space on each database node.

    [root@dbn01 ~]# lsblk
    Figure 3-5 lsblk

  2. Run lvcreate to create a 200 GB logical volume lv_oracle on the volume group fusioncube. Then, run the lsblk command to check whether the logical volume is successfully created.

    [root@dbn01 ~]# lvcreate -L +200G -n lv_oracle fusioncube
    Figure 3-6 Creating a logical volume of 200 GB

  3. Format the logical volume lv_oracle to the ext4 file system.

    [root@dbn01 ~]# mkfs.ext4 /dev/fusioncube/lv_oracle
    Figure 3-7 Formatting the file system

  4. Create the database installation directory /u01, mount the lv_oracle logical volume to the /u01 directory. Then, check whether the logical volume is successfully mounted.

    [root@dbn01 ~]# mkdir -p /u01 
    [root@dbn01 ~]# mount /dev/fusioncube/lv_oracle /u01/ 
    [root@dbn01 ~]# lsblk
    Figure 3-8 Creating an installation directory and mounting the logical volume

  5. Open the /etc/fstab file, and add the lv_oracle mount configuration (the following content in bold) to ensure that the mounted partition will not be lost after restart.

    [root@dbn01 ~]# vim /etc/fstab 
    # /etc/fstab
    # Created by anaconda on Mon Jul 16 19:44:51 2018
    #
    # Accessible filesystems, by reference, are maintained under '/dev/disk'
    # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
    #
    /dev/mapper/fusioncube-root /                       ext4    defaults        1 1
    UUID=188c7fe7-b611-42e4-a7a1-5ef874a3ad60 /boot                   ext4    defaults        1 2
    UUID=50D4-D5CD          /boot/efi               vfat    defaults,uid=0,gid=0,umask=0077,shortname=winnt 0 0
    /dev/mapper/fusioncube-opt /opt                    ext4    defaults        1 2
    /dev/mapper/fusioncube-usr /usr                    ext4    defaults        1 2
    /dev/mapper/fusioncube-var_kbox /var/crash              ext4    defaults        1 2
    /dev/mapper/fusioncube-var_log /var/log                ext4    defaults        1 2
    /dev/mapper/fusioncube-swap swap                    swap    defaults        0 0
    /dev/mapper/fusioncube-lv_oracle /u01           ext4    defaults        1 2
    tmpfs                   /dev/shm                tmpfs   defaults        0 0
    devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
    sysfs                   /sys                    sysfs   defaults        0 0
    proc                    /proc                   proc    defaults        0 0
    
    Figure 3-9 Editing the /etc/fstab file

    If the database node uses the Red Hat Enterprise Linux 7 OS, /dev/shm is mounted by default when the OS is started. The default size of /dev/shm is half of the physical memory, but /dev/shm is not displayed in /etc/fstab. If there is no special requirement for the capacity, use the default value.

Translation
Download
Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 25000

Downloads: 35

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