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


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


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).
Oracle RAC Shared Volume Plan

Oracle RAC Shared Volume Plan

Communicate with the customer to determine the quantity and sizes of volumes in the OCR (Oracle Cluster Registry) area, whether an independent flash recovery area is required and the capacity of the area if required, the quantity and sizes of the data area volumes, and the redundancy policy of each disk group.

  • The OCR area contains key cluster configuration information including the public and dedicated network configuration information. It is recommended that three OCR volumes be used for a two-node cluster and the size of each volume be 30 GB.
  • The FRA (flash recovery area) stores specific restoration files to manage database restoration in a centralized and simplified manner. This area prevents disk space exhaustion from affecting all instances when multiple instances are archived to the same disk. That is, this area reduces the scope of the services affected. The recommended capacity of the flash recovery area is 800 GB. The capacity can be adjusted based on service requirements.
  • The data area stores data. The disk group size is determined based on the service requirements. It is recommended that the total number of disks in the data area be 20 to 100. The capacity of a single disk is calculated based on the available capacity of the storage pool and the expansion capacity to be planned. To improve I/O performance, the customer can store redo log groups and data separately based on the service requirements.
  • The Oracle ASM provides three redundancy policies:
    • External redundancy:

      The Oracle system does not manage disk mirrors. The redundancy function is provided by external storage systems, such as RAID arrays. The valid disk space is the total space of all disks.

    • Normal redundancy:

      The Oracle system provides two mirrors to protect data (one mirror backup). The valid disk space is half of the total disk space.

    • High redundancy:

      The Oracle system provides three mirrors to protect data (two mirror backups) to improve performance and data security. At least three disks are required, and the valid disk space is a third of the total disk space. Although the redundancy level is improved, the hardware cost is the highest among the three redundancy policies.

    The following table describes the shared volume plan.

    Disk Group



    Redundancy Policy



    300 GB



    300 GB



    30 GB



    30 GB


    30 GB



    500 GB


Updated: 2019-02-01

Document ID: EDOC1100053123

Views: 13825

Downloads: 14

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