ASM level of redundancy

Similar Questions

• Change the level of redundancy

  I have a RAC database, using 1 disk group.
  This disk group using HIGH redundancy. It has three discs.
  
  Can I change the redundancy externally?
  I want to do it because I need to remove 2 of the 3 disks.

  Hello

  You are right, that the current DG should be destroyed anyway in order to "change" the level of redundancy for the disk group.
  The two options are:
  -The data migration to a new group of disks created with the desired level of redundancy.
  -Perform a backup on the database current DG you remove, re-create it with different level of redundancy then do restore/recovery.

  I hope this helps as well.
  Kind regards
  József

• 11 GR 2 Grid Infrastructure install - with normal redundancy ASM disk group requires 3 disks?

  
  Hello

  I want to install 11 GR 2 grid Infrastructure in a new environment in cluster - 2 nodes). I use the 11.2.0.4 GI Installer on Oracle Linux 6.5 x 86-64

  However when it is in the installer of GI, it comes to choose the storage Option - I choose ASM disk groups.

  Then change the path of discovery to pick up my candidate ASM disks.

  I enter the disk group name SIR give Normal redundancy, choose 2 discs of candidate and then press < next > to Setup.

  However, I gives me the message

  [INS-30510] Insufficient number of ASM disks selected

  The number of selected disks was inadequate for the level of redundancy selected

  For a disk group with redundancy level "Normal" disks at least "3" are recommended

  I always thought that Redunancy Normal required only 2 discs and high redundancy requires 3 disks?

  No idea what is gpoing?

  Thank you

  Jim

  Consult the following notes for how to move:

  Note 1638177.1 and 428681.1

  Concerning

  Thomas

• QUESTION OF REDUNDANCY NORMAL ASM

  Hi all
  
  Document Oracle ASM NORMAL QUESTION of REDUNDANCY [1480954.1 ID] says the statement, I find it difficult to understand the line which is marked in italics below.
  
  To determine the appropriate size of a diskgroup which is protected with redundancy of ASM, sufficient free space must exist in the diskgroup

  so that when a drive goes down, it can automatically rebuild the contents of the drive failed on another drive in the diskgroup. The database should stay online if sufficient space is available

  . The amount of space required to ensure ASM can restore redundancy if there is no disc is in the REQUIRED_MIRROR_FREE_MB column in the view V$ ASM_DISKGROUP. The amount of free space that can be used safely in a disk group, taking into account, mirroring and still be able to restore redundancy after a drive failure is in the USABLE_FILE_MB column in the view V$ ASM_DISKGROUP. USABLE_FILE_MB must always be greater than zero. If USABLE_FILE_MB falls below zero, most records should be added to the disk group.
  
  DOUBT: why what he have reconstitute the content of the disc failed on another drive in the diskgroup when scopes in mirror and I do not understand when the disc itself is failed how they can access it and rebuild its contents to another drive.
  
  
  Concerning

  DOUBT: why need restore the contents of the drive failed on another drive in the diskgroup when there mirrored scopes

  because the data on the failed drive is not more in the opposite direction (no additional copies) and to ensure a level of normal redundancy, we'll build a new mirror copy of data

  I do not understand when the disc itself broke down how they can access it and rebuild its contents to another drive.

  data always available, mirrored

  to explain it simply:

  everything is stored with 2 copies (original + mirror)
  When 1 is lost, a new copy will be rebuilt among others the 1, so there will be 2 copies again

• Is this normal in "normal redundancy?

  The GI version: 11.2.0.4 (RAC 3-node)

  OS: Oracle Linux 6.4

  Storage EMC Symmetrix VMAX

  I created a diskgroup with normal redundancy as shown below.

  10 each = 5000GB 500 GB LUN

  CREATE DISKGROUP DATA_DG1

  NORMAL REDUNDANCY

  DISC

  "ORCL:DATA_D1,"

  "ORCL:DATA_D2,"

  "ORCL:DATA_D3,"

  "ORCL:DATA_D4,"

  "ORCL:DATA_D5,"

  "ORCL:DATA_D6,"

  "ORCL:DATA_D7,"

  "ORCL:DATA_D8,"

  "ORCL:DATA_D9,"

  'ORCL:DATA_D10 '.

  ATTRIBUTE 'au_size' = "4 M";

  DiskGroup created.

  Given that it was normal, I was expecting half of gross space 5000 GB = 2.5 terabytes of usable space. But, the query below shows the output, I myself only 2.19 terabytes of usable (2249,86 GB) space. About 250GB short of what I expected. So where's my advantage 250 GB?

  SQL > select name, TYPE, 1024/1024/TOTAL_MB, FREE_MB/1024/1024, USABLE_FILE_MB/1024/1024 of v$ asm_diskgroup where name = 'DATA_DG1 ';

  NAME TYPE TOTAL_MB/1024/1024 FREE_MB/1024/1024 USABLE_FILE_MB/1024/1024

  ------------------------------ ------ ------------------ ----------------- ------------------------

  NORMAL DATA_DG1 4.8828125 4.8825531 2.19713593

  The amount of usable file space is equal to the amount of free disk space subtracted from the amount of disk space required to restore redundancy after failure divided by the level of redundancy of the disk group that is in your case.

  Run:

  select trunc((free_mb - required_mirror_free_mb) / 2) as useable from v$asm_diskgroup where name='DATA_DG1';
  

  Source: http://prutser.wordpress.com/2013/01/03/demystifying-asm-required_mirror_free_mb-and-usable_file_mb/

• Difference between ADVM Volume and filesystem ACFS ASM disk group

  Q1. What is the difference between an ASM disk group and a Volume of ADVM?

  In my opinion, an ASM disk group is actually a logical volume to the database (including the FRA files) files.

  11 GR 2 appears to have introduced the notions of volumes ADVM and filesystems ACFS.

  11 GR 2 ASM disk group can contain:

  • ASM disks
  • Volumes ADVM
  • Filesystems ACFS

  Q2. ADVM volumes appear to be dynamic volumes.

  However is it therefore not effectively overlaying a logical volume (the volume ADVM) under ASM disk group (conceptually a logical volume as well)?

  Even worse, if you left the ASM disk group redundancy in hardware RAID / SAN level (as recommended Oracle), you actually have 3 layers of logical disk? (ASM on top of ADVM on top of RAID/SAN)?

  Q3. If it is 2 layers of logical disk (i.e. on top of ADVM ASM), what makes this better than 2 layers using a 3rd party volume manager (for example the DSO at the top of the 3rd party LVM) - something Oracle encourages against?

  Q4. ACFS file systems, seem to be file systems clustered for not including ORACLE_HOMEs database files, application exe etc (but NOT GRID_HOME, OS root, OCR or voting records)

  Can you create / modify filesystems ACFS using ASM.

  The diagram of topology of oracle for ASM in ASM 11 GR 2 administration guide, says ACF in ASM. I'm not sure about that if ACFS belongs to ASM or ASM is located at the top of the ACF?

  Q5. Connected to the 4th quarter. There seems to be a number of different ways, ACFS file systems can be created? Which of this is the valid methods?

  • Thanks to ASM?
  • through native OS file system creation?
  • through OEM?
  • through acfsutil?

  my head explodes

  Any help and clarification appreciated

  Jim

  
  

  Q1 - volume ADVM is a type of special file created at the DG of the DSO.  Once created, it creates a block device on the BONE itself which can be used as any other block device.  http://docs.Oracle.com/CD/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000

  Q2 - the asm disk group is a group of disks, not really a logical volume.  It combines the attributes of both when it is used for purposes of database as the database and some other applications know how to talk about Protocol 'ASM '.  However, you won't find all the versatile applications that can do.  In addition, some clients prefer to deal directly with files and devices of volume systems which ADVM is forced to make.  In your thinking, you have 3 layers of logical disk, but each of them provides features and different attributes.  This is not a bad thing, though, as each has a slightly different purpose - os file system\device, specific database and storage-centric.

  Q3 - ADVM is specifically developed to extend the features of the DSO for use by General applications of BONE.  It includes the performance of database features and is tuned to work well in this situation.  Because it is developed in-house, it benefits from the design of ASM model.  In addition, rather than having to communicate with several vendors for support, your support is limited to calling Oracle, a single window.

  Q4 - you can create and modify filesystems ACFS by using command line tools and the ASMCA.  Creation and modification of logical volumes coming through SQL (ASM), asmcmd and ASMCA.  EM can also be used for the two elements.  ACFS is located at the top of the ADVM, which is a file in an ASM disk group.  ACFS is aware of the characteristics of the ASM\ADVM volumes and tunes it's IO make best use of these features.

  Q5 - several ways:

  1) connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out.  This creates an ADVM volume.  Then, put in shape volume using the "mkfs" (* nix) or acfsformat (windows).

  (2) use ASMCA - a GUI to create volume and a file system.  Probably the easiest if your head is explosion.

  (3) use "asmcmd" to create a volume and 'mkfs' to put in shape file ACFS system.

  Here is information on the ASMCA, with examples:

  http://docs.Oracle.com/CD/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348

  Information about the command line tools, with examples:

  Basic steps to manage systems Oracle ACFS

• The ASM diskgroup in exadata space question

  All,
  
  I have an environment exadata 1 CCR node with 3 knots of strorage.
  
  My RECO ASM diskgroup is constantly showing the problems of space... Always higher than 80%.
  
  I just want to get a Board if I can remove mirroring and recover the space... Even though I know that the result of the deletion of the mirroring...
  
  Can I reduce the diskgroup RECO and create an another diskgroup?
  
  I want just a few ideas to do this without great risk involved...

  You may want to consider these MOS notes for more information on resizing the griddisks:
  Resize diskgroup without downtime to Exadata (Doc ID 1272569.1)
  How to resize the disk drive/grid ASM in environment Exadata (Doc ID 1245494.1)

  As others have mentioned, there is no way to change the level of redundancy in ASM, so you need to delete and re-create the diskgroup if you want to change to redundancy. We strongly discourage the use of EXTERNAL with Exadata redundancy.

• ASM vs San raid which to adopt

  Hello
  
  We have a system using ASM and San drive. San has a hardware raid, while the DSO has also do the same thing. Because according to my understand its function. Strip and any mirror. Do you think we have several raids in the system and we should disable hardware raid. Also I thing hardware raid is raid 4. Please correct me if I'm wrong
  
  concerning
  Nick

  RAID 1 + 0 or 0 + 1 is an implementation of striping and mirroring.
  RAID 5 is an implementation of aggregation by band with parity (where the parity strip is scattered between the discs, with RAID 4 parity stripes are on specific disks)
  See: http://www.baarf.com

  Please, mind, than the baarf Web site focuses on the decrease in performance (writing) of the use of RAID levels with parity. Even with the SAN, it is still quite true. (it is inherent on the way to parity is implemented)

  ASM normal redundancy is essentially a mirror application. The implementation of normal redundancy ASM subtly different way works mirrored RAID.

  This means having RAID 1 + 0 / 1 + 0 on SAN level is a way of mirroring, and having normal redundancy ASM is another way to have copies mirror blocks, which would mean that having RAID mirroring on the normal SAN and level of redundancy at the ASM level means you have 4 copies on the same storage box.

  So I would say that there is little benefit to have normal redundancy ASM on top a stripeset mirrored.

  As an adviser what to do: most ASM implementations use external redundancy, which means the redundancy of the San is used. I think it makes sense.
  With the help of normal redundancy makes sense when you use local drives (non-RAID), or when having multiple SAN.

• dissappearing asm space

  Oracle 11.2.0.4 SE a 64-bit

  Standalone ASM 11.2.0.4 - no CARS, no grouping

  Oracle Linux 5.6

  Database had two DGs in ASM.  External redundancy, another normal redundancy with two failure groups.  A group of failure was on local SSD on the server. We have been short on space and limited by these local drives, so created a third DG in order to replace the constraint...  This one disc, external redundancy.  Disks to look like this.  The SMALL DG is the one who is forced to the internal SSD.  DG DATA2 is his replacement.

  GROUP_NUMBER DISK_NUMBER SIZE_GB REDUNC DISK_NAME FAILGROUP GROUP_NAME

  ------------ ----------- ----------- ---------- ------ -------------------- ---------------

  3 LARGE EXTERN 0 950 LARGE_0000 LARGE_0000

  4 SMALL 0 149.863281 NORMAL SMALL_FIOA SSD_GROUP

  4 SMALL 1 149.863281 NORMAL SMALL_FIOB SSD_GROUP

  4 SMALL 3 149.011719 NORMAL SMALL_FIOC SSD_GROUP

  4 SMALL 6 150 NORMAL SAN_GROUP SMALL_0006

  4 SMALL 7 150 NORMAL SAN_GROUP SMALL_0007

  4 SMALL 8 150 NORMAL SAN_GROUP SMALL_0008

  5 DATA2 EXTERN 0 500 DATA2_0000 DATA2_0000

  Yesterday, I finished moving all the data and temporary files from SMALL to DATA2.  The only files left on the SMALL are control files, which I hope to move today.

  Now the question.  I have a task that runs every morning at 0630 to gather various metrics of the use of disk file system and ASM. The result of this work is recorded and used to fill a daily tracking spreadsheet. Yesterday, I did an extra run after I finished moving all the data files (but before you move the temporary files). At this point, the SMALL DG showed 337,8 GB of usable space.  After that, I created a new temp TS (TEMP2) with its files on DATA2 and dropped the old a little.  I capture info use disk at this stage.

  This morning I got a big surprise.  The SMALL DG relates now only 74.4 GB of usable space.  I double checked its contents using "asmcmd" and verified that the only file on it's a db control file and its alias.

  The command to capture its use ASM is

  asmcmd lsdg | awk ' {print $13 "" $2 "" $7 "" $8 "" $10}' > > $logfile

  with this result:

  Name Type Total_MB Free_MB Usable_file_MB

  DATA2 / 512000 154640 154640 EXTERN

  LARGE / EXTERN 972800 33915 33915

  SMALL / NORMAL 920308 OF NTA 305895 76147

  Output power of "lsdg;

  State Type sector Rebal to Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files name of the block

  EXTERN MOUNTED N 512 4096 1048576 512000 154640 0 154640 0 N DATA2.

  EXTERN MOUNTED N 512 4096 1048576 972800 33915 0 33915 0 N GRAND.

  NORMAL CLIMB N 512 4096 1048576 920308 OF NTA 305895 153600 76147 0 N SMALL.

  I don't know if this will solve the problem, but perhaps that it was tyring:

  ALTER DISKGROUP SMALL CHECK REPAIRS;

• Syntax to drop several disks in a single command ASM

  Hello

  We have 11.2.0.2 with 2 RAC on AIX 7.1 knots. We have the starts in ASM with NORMAL redundancy and the diskgroup has 100 (50 for a failgroup) and 50 for an another failgroup discs.

  We will drop 10 discs (5 a failgroup) and 5 from other failgroup since this diskgroup, so that all failgroups have the same number of disks (and sizes also).

  So, I need the syntax to drop all ASM 10 of the same diskgroup disks in a single request. Could help me in this area, please?

  I can try to use 10 commands, one for each disc to give up but, after the execution of each command/disc, the operation of rate rebalancing will take place and that will make us wait until the re - balance finish to execute the next command in the drop. To avoid time taking orders 10 running one by one, I would drop them all in a single command.

  for example, the discs that we will give up are below:

  Failgroup: FG1

  PATH NAME

  ----------------------- ---------------------

  / dev/DATAM_L0203_ORCLFG1 NAME ORCL_DATOS_0150

  / dev/DATAM_L0204_ORCLFG1 NAME ORCL_DATOS_0151

  / dev/DATAM_L0205_ORCLFG1 NAME ORCL_DATOS_0152

  / dev/DATAM_L0206_ORCLFG1 NAME ORCL_DATOS_0153

  / dev/DATAM_L0207_ORCLFG1 NAME ORCL_DATOS_0154

  Failgroup: FG2

  PATH NAME

  ----------------------- ---------------------

  / dev/DATAL_L0203_ORCLFG2 NAME ORCL_DATOS_0184

  / dev/DATAL_L0204_ORCLFG2 NAME ORCL_DATOS_0184

  / dev/DATAL_L0205_ORCLFG2 NAME ORCL_DATOS_0184

  / dev/DATAL_L0206_ORCLFG2 NAME ORCL_DATOS_0184

  / dev/DATAL_L0207_ORCLFG2 NAME ORCL_DATOS_0184

  Thank you very much

  for example

  alter diskgroup diskgroup_name drop disk ' / dev/oracle/disk197 ',' oracle/dev/disk198 ',' oracle/dev/disk199 ".

  Another good resource is lower. You can also use the names of disk instead of paths

  ORACLE-BASE - Automatic Storage Management (ASM) in Oracle Database 10g

• Half Rack exadata with DBFS_DG have normal redundancy?

  My understanding is that one install scripts command automatically the value of the level of redundancy for the diskgroup DBFS_DG. I think I had actually foud this in the code of gridsteps.pm function CreateASMDiskgroups() onecommand. For an eighth and a quarter rack, it's Normal for half and full, it is high. This is to ensure that critical OCR and vote the files are backed up as far as possible. But recently I came across several facilities half rack with DBFS_DG redundancy as usual. Is it possible to replace this or does this mean that the grid software has been reinstalled manually at some point?

  It's about x 2-2 half baskets. Grateful if someone knows if there is a way, it could happen through an implementation of the standard onecommand.

  OneCommand creates DBFS_DG in normal redundancy each time.  If you are on a half or a full rack with high diskgroup redundancy, he moves the OCR and files to this vote diskgroup.  This happens at the stage of CreateASMDiskgroups of onecommand.

• Installation of VMware server redundent

  We run a server VMware (VMware ESX Server version 3.5.0 Update 2).  I have about 8 virtual machines running on the server.  We backup each virtual machine in the virtual machine, not outside of it.  I want to buy an additional VMware Server which will provide redundancy.  The second server VMware will also store some VMS, but there will be enough space on the two servers if you die, I can restore to another.  Someone please lead me in the right direction?  I.E. - is there a component of VMware that I need to follow both servers support between them?  Outside the redundant material, purchase another license complete for VMWare ESX Server?

  Hello

  Need you depends on the level of redundancy, you need.  Here are some examples... If you have X ESX hosts you will need X licenses regardless of the method of redundancy.

  Using VMware HA failover mode, this requires a shared either NFS over TCP (NAS), iSCSI, or SAN storage. Some of the features of type available non - NAS NAS are HP LeftHand Networks VSA and Xtravirt XVS. The latter two run from your ESX and VMS host and maintain redundancy between the nodes.

  Redundancy via SAN/NAS replication is also available and VMware SRM fits in do SAN/NAS to SAN/NAS replication.

  Redundancy through replication using elements such as Veeam Backup and Vizioncore vReplicator, which are tools of software replication to replicate virtual machines from one node to another.

  Redundancy via the backup and restore. This method VMs from one host backups and restores to another host. It is very similar to the replication but heavier.

  How redundancy you want depends a bit much you are willing to spend, but if you have 1 node and you want to replicate to another node, you need at least 2 licenses of VMware ESX to get there.

  Best regards

  Edward L. Haletky

  VMware communities user moderator

  ====

  Author of the book "VMWare ESX Server in the enterprise: planning and securing virtualization servers, Copyright 2008 Pearson Education.»

  Blue gears and SearchVMware Pro Articles: http://www.astroarch.com/wiki/index.php/Blog_Roll

  Security Virtualization top of page links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

• Mirroring of the ASM

  Hello
  
  I have little doubt.
  
  Lets say we configure our ASM environment with HIGH redundancy, which will create 3 copies. My doubt is which does this job of mirroring. I read that ASM is not involved in the ADR process and writing. DBWR merely the writiting. What makes the mirroring of the allocation unit.
  
  Thanking you
  Rakesh

  Which back ground process does all. Is it RBAL or another process

  ASM will maintain redundancy by allocating extended to other group failed as soon as it allocates measure first.
  ASM instance has two new background process types, one for the coordination of the activity of rebalancing of the Group disk and one for data ORB0, ORB1 movements. These perform the movements of measurement of actual data of rebalancing.

• 11g ASM with 10g RDBMS?

  Hello-
  
  My database is running to 10.2.0.4. I want to install DSO and gradually convert the one-at-a-time tablespaces start ASM. Can I ASM 11.1.0.7 and the DB still be to 10.2.0.4?
  
  Thank you!

  Yes. It's quite possible. Make sure to install in a House separate from the database. This will make it easier to apply updates and patches to asm level without affecting the database host.

• Application of quorum

  Environment

  2 RAC cluster nodes with each container:

  ----------------------------------------

  Oracle Linux 6 update 5 (x 86-64)

  Oracle Grid Infrastructure 12R1 (12.1.0.2.0)

  12R1 database Oracle (12.1.0.2.0)

  I'm not understanding the role of the College in the Group of lack of quorum for voting with Oracle ASM files.

  Failure of groups (FG) assure that there is a separation of the risk you are trying to mitigate.   The separation is to scale with user data.  Vote files, the file is separated on a disk for each FG in the Group Disk (DG).  If voting files are stored on a disk group (DG) to the normal dismissal.  A minimum of two FGs is required.  It is recommended that 3 FGs serve.  It's so partner status Table (PST) may have at least one other FG where PST is maintain by comparison.  It is in the case of a failure of FG.  Must the FGs be QUORUM which store files to vote?  What is the role of the College? When is it necessary?

  Hello

  I'll start with what the Quorum means:

  The quorum is the minimum number of members (majority) of a game, necessary to avoid a failure. (COMPUTER concept)

  A quorum is a lot like Votedisk Quorum Quorum OCR, network Quorum, Quorum PST, etc.

  We must separate this quorum, we are concerned.

  The PST Quorum is different from the Quorum of Votedisk, well think everything works toogheter.

  Quorum PST:

  A PST file contains information on all the disks in a Diskgroup ASM - number of disk, Disk Status, disk number, the heart rate info and Failgroup Info partner.

  A disk group must be able to access a quorum of the Tables of status partner (PST) to mount the diskgroup.

  When diskgroup mount is requested the instance reads all disks in the disk group to find and verify all available PST. Once it checks that there is enough PSTs for quorum, he set up the disk group.

  There is a good post here: ASM support Guy: partnership and the State Table

  Votedisk quorum:

  Is a minimum number of votes for cluster is operational. There is still a quorum of votedisk.

  When you configure votedisk in normal redundancy you 3 Votedisk one in each Failgroup. For cluster is operational you need of at least a quorum with 2 online voting for the cluster are online.

  Quorum Failgroup (clause):

  Quorum Failgroup is an implementation of a Diskgroup option.

  This option do not confuse with the Quorum of voting, because the Quorum of voting and Quorum Failgroup are different things.

  For example: in a Normal Redudancy diskgroup can I lost my Failgroup Quorum, and the Cluster will stay in line with 2 Failgroup regular, this Quorum failgroup is an installation program.

  Named as 'Failgroup Quorum' a failegroup to a specific purpose which is store only the Votedisk due to deployment of the infrastructure of the Oracle.

  Is no obligation to use "Quorum Failgroup' in a Diskgroup containing votedisk.

  Now, back to your question:

  If your failure groups have only 1 ASM disk then should not the recommendation to use high redundancy (5 groups of failure) so in the case of a disk failure ASM a quorum of PST (3 PST files) would be possible?

  About Quorum PTS: You need must be aware that if you have 5 PST, you will need at least a quorum with 3 PST to mount his Diskgroup.

  If you have 5 Failgroup and each Failgroup has ASMDISK that one alone, you'll have a STP by ASMDISK that support you lost at least 2 PST to make a Quorum with 3 PST and keep mounted Diskgroup or fix it.

  The bold italic Oracle documentation above seems to say that if you allocate 3 devices in disc 2 will be used by groups of normal redundancy failure. In addition, a group of lack of quorum will exist who will use all disk devices.  What does that mean?

  I don't know what documents are saying is so confused. I'll try to contact some employee of Oracle to check it out.

  But will attempt to clarify some things:

  Suppose you install a Diskgroup as follows:

  DATA DiskGroup

  Failgroup data01

  * / dev/hdisk1 and/dev/hdisk2

  Failgroup data02

  * / dev/hdisk3 and/dev/hdisk4

  Failgroup data03

  * / dev/hdisk5 and/dev/hdisk6

  Quorum Failgroup data_quroum

  * / nfs/votedisk

  When you add Votedisk on this WHAT DATA diskgroup, the CSSD will store as follow:

  CSSD will randomly choose an asmdisk by votedisk Failgroup and magazine on the subject, but always chooses an ASMDISK of Failgroup of Quorum (if it exists).

  Therefore, after you add votedisk below diskgroup that you have:
  * Failgroup data01 (/ dev/hdisk2)

  * Failgroup data03 (/ dev/hdisk5)

  * Failgroup data_quorum (votedisk/nfs /)

  Mount diskgroup data, you must failgroup data01, data03 and data_quorum available in the diskgroup mount, otherwise diskgroup does not rise.

  On Documentation (https://docs.oracle.com/database/121/CWADD/votocr.htm#CWADD91889) is a bit of confusion:

  Normal redundancy

  The level of redundancy you choose for the Oracle ASM disk group determines how Oracle ASM mirrors the disk group files and determines the number of disks and the amount of disk space you need. If the files with the right to vote in a disk group, groups of disks that contain Oracle Clusterware (OCR and vote files) files have a more minimum number of groups of failure than other disk groups because with voting rights are stored in the default quorum groups.

  What he says is: when using Failgroup of Quorum, you will have a more minimal number of failure than other disk groups...

  But remember that qorum Failgroup is optional for those who use a single storage or an odd number of H/w storage.

  For Oracle Clusterware files, a normal redundancy disk group requires a minimum of three disk devices (two of the three discs are used by groups of failure and all three disks are used by the default quorum group) and provides three files with right to vote and a mirror of the OCR OCR. When you use a normal disk of redundancy group, the cluster can survive the loss of the group a failure.

  Try to clarify:

  -Votedisk in Diskgroup with normal redundancy requires three drive devices. (When using Failgroup Quorum: you will have two of the three disk used by regular failgroup and one of the three discs are used by Quorum Failgroup but all three discs (regular failgroup and quorum that store votedisk) count when mount the diskgroup.)

  - OCR and a mirror of OCR:

  It was really confusing. Because the mirror of the OCR must be placed in a different diskgroup because OCR is stored similar to how Oracle database files are stored. Scopes are spread across all disks in the diskgroup.

  I don't know what he's talking about. If measure on diskgroup redundancy mirror or mirror of the OCR.

  By as note and especially the documentation says it's not possible store OCR, and OCR mirror on diskgroup even

  RAC FAQ (Doc ID 220970.1)

  How the registry of Cluster Oracle (OCR) is retained when using ASM?

  And (https://docs.oracle.com/database/121/CWADD/votocr.htm#CWADD90964)

  * At least two places of OCR if OCR is configured on an Oracle ASM disk group. You must configure OCR in two groups of independent labels. In general, it is the recovery area and work space.

  High redundancy:

  For the Oracle Clusterware, a disk group files high redundancy requires a minimum of five disk drives (three of the five discs are used by groups of failure and all five disks are used by the default quorum group) and provides five files with right to vote and an OCR and two mirrors of the OCR. With high redundancy, the cluster can survive the loss of two failure groups.

  Three of the five discs are used? and two mirrors of OCR? In a Diskgroup single?

  Now things goes bad.

  As much as I can test and see how Quorum Votedisk four (but not three) of five disks are used and all five counties.