Oracle^® SuperCluster Quorum Disk Manager

Adding an Oracle Exadata Storage Server and Expanding an Existing High Redundancy Disk Group

When you add a storage server that uses quorum disks, you should relocate a voting file from a database node to the newly added storage server.

1. Add the Exadata storage server.

   Refer to the following document for those instructions:

   http://docs.oracle.com/cd/E50790_01/doc/doc.121/e51951/storage.htm#DBMMN22922

   In the example below, the new storage server that is being added is called "celadm04".

2. After the storage server is added, verify the new fail group from v$asm_disk.

   SQL> select distinct failgroup from v$asm_disk;
   FAILGROUP
   ------------------------------
   ADM01
   ADM02
   CELADM01
   CELADM02
   CELADM03
   CELADM04 

3. Verify at least one database node has a quorum disk containing a voting file.

   $ crsctl query css votedisk
   ##  STATE    File Universal Id                File Name Disk group
   --  -----    -----------------                --------- --------- 
   1. ONLINE   834ee5a8f5054f12bf47210c51ecb8f4 o/192.168.12.125;192.168.12.126/DATAC5_CD_00_celadm01) [DATAC5] 
   2. ONLINE   f4af2213d9964f0bbfa30b2ba711b475 (o/192.168.12.127;192.168.12.128/DATAC5_CD_00_celadm02) [DATAC5] 
   3. ONLINE   ed61778df2964f37bf1d53ea03cd7173 (o/192.168.12.129;192.168.12.130/DATAC5_CD_00_celadm03) [DATAC5] 
   4. ONLINE   bfe1c3aa91334f16bf78ee7d33ad77e0 (/dev/exadata_quorum/QD_DATAC5_ADM01) [DATAC5] 
   5. ONLINE   a3a56e7145694f75bf21751520b226ef (/dev/exadata_quorum/QD_DATAC5_ADM02) [DATAC5]
   Located 5 voting disk(s). 

   The example above shows there are two quorum disks with voting files on two database nodes.

4. Drop one of the quorum disks.

   SQL> alter diskgroup datac5 drop quorum disk QD_DATAC5_ADM01; 

   The voting file on the dropped quorum disk will be relocated automatically to the newly added storage server by the Grid Infrastructure as part of the voting file refresh. You can verify this as follows:

   $ crsctl query css votedisk
   ##  STATE    File Universal Id                File Name Disk group
   --  -----    -----------------                --------- --------- 
   1. ONLINE   834ee5a8f5054f12bf47210c51ecb8f4 (o/192.168.12.125;192.168.12.126/DATAC5_CD_00_celadm01) [DATAC5] 
   2. ONLINE   f4af2213d9964f0bbfa30b2ba711b475 (o/192.168.12.127;192.168.12.128/DATAC5_CD_00_celadm02) [DATAC5] 
   3. ONLINE   ed61778df2964f37bf1d53ea03cd7173 (o/192.168.12.129;192.168.12.130/DATAC5_CD_00_celadm03) [DATAC5] 
   4. ONLINE   a3a56e7145694f75bf21751520b226ef (/dev/exadata_quorum/QD_DATAC5_ADM02) [DATAC5] 
   5. ONLINE   ab5aefd60cf84fe9bff6541b16e33787 (o/192.168.12.131;192.168.12.132/DATAC5_CD_00_celadm04) [DATAC5] 

5. Delete the quorum device.

   Run the following command from the database node:

   /opt/oracle.SupportTools/quorumdiskmgr --delete --device [--asm-disk-group asm_disk_group] [--host-name host_name]

6. Delete the target.

   Run the following command from the database domain:

   /opt/oracle.SupportTools/quorumdiskmgr --delete --target [--asm-disk-group asm_disk_group]

7. Delete the configuration.

   Run the following command from the database domain:

   /opt/oracle.SupportTools/quorumdiskmgr --delete –config