4.3.10.2 ALTER DISKGROUP

This command alters attributes for an existing Oracle ASM disk group.

Syntax

ALTER DISKGROUP
   { ACFSNAME=acfs_name |
     ACFSPATH=acfs_path |
     ACFSSIZE=acfs_size |
     CELLLIST='cell_list' |
     DISKGROUPNAME=diskgroup_name |
     DISKGROUPLOCATION=diskgroup_location |
     DISKGROUPSIZE=diskgroup_size |
     OCRVOTE=ocr_voting_disks_included |
     QUORUMDISK=quorum_disks_included |
     REDUNDANCY=redundancy_level |
     SLICESIZE=slice_size |
     SPARSE=sparse } ...
WHERE 
  { ID=diskgroup_id |
    CLUSTERNUMBER=cluster_number DISKGROUPNAME=diskgroup_name |
    CLUSTERNAME=cluster_name DISKGROUPNAME=diskgroup_name |
    CLUSTERID=cluster_id DISKGROUPNAME=diskgroup_name }

Arguments

You can modify the following attributes of an Oracle ASM disk group:

• ACFSNAME : Specifies a new name for the Oracle ACFS volume on this disk group

• ACFSPATH : Specifies the new path for the Oracle ACFS file system

• ACFSSIZE : Specifies a new size for the Oracle ACFS volume on this disk group

• CELLLIST : A comma separated list of cells for this disk group, enclosed in single quotes

• DISKGROUPNAME : Specifies a new name for the disk group

• DISKGROUPLOCATION : Specifies the media type where the disk group is located. The valid values are FLASHDISK or HARDDISK. The default value is HARDDISK.

  The same disk group location is recommended for all non-RECO disk groups across all clusters in the Exadata configuration file (es.xml). If the RECO disk group location is FLASHDISK, then FLASHDISK is the recommended location for all disk groups.

• DISKGROUPSIZE : Specifies a new size for the disk group

• OCRVOTE : A boolean variable, where TRUE indicates the disk group should store the OCR and voting disks for the cluster.

• QUORUMDISK : A boolean variable, where TRUE indicates the disk group requires a quorum

• REDUNDANCY : Specifies the redundancy level for the disk group. The valid values are NORMAL or HIGH.

• SLICESIZE : Specifies the slice size on disk for each grid disk for this disk group.

• SPARSE : A boolean variable, where TRUE indicates this should be sparse disk group.

The following arguments are available in the WHERE clause:

• ID : Specifies the es.xml ID for the disk group

• CLUSTERNUMBER : Specifies the cluster number in the es.xml, starting at 1

• CLUSTERNAME : Specifies the name of the cluster

• CLUSTERID : Specifies the es.xml ID of the cluster

• DISKGROUPNAME : Specifies the name of the disk group

Usage Notes

• With the ALTER DISKGROUP command, you can only deploy the following modifications to an existing disk group:

  • You can alter the size of an existing disk group by setting the DISKGROUPSIZE attribute.

  • You can change the storage servers that contain the disk group by setting the CELLLIST attribute. However, if you remove a storage server from a disk group, you must ensure that the remaining storage servers have enough space to accommodate the existing data.

  Changes to all other disk group attributes may only be saved to the OEDA XML configuration file (es.xml). Consequently, you cannot use the ALTER DISKGROUP command in conjunction with the DEPLOY ACTIONS command to change the name of an existing disk group, for example.

• If you modify the redundancy, the volume size will be maintained, however the slice size will be recalculated.

Example 4-21 Resizing an Oracle ASM Disk Group Using OEDACLI

This example shows how to resize an existing Oracle ASM disk group using OEDACLI.

1. Load the OEDA XML configuration file.

   oedacli> LOAD FILE NAME=Oracle-test.xml 
   SUCCESS - file loaded OK 
   Customer : ora07adm01 - Oracle

2. Use the command LIST DISKGROUPS to view the disk group details.

   oedacli> LIST DISKGROUPS
   version : "PhysicalLayoutLegacy" 
   diskGroupName : "DBFS_DG" 
   redundancy : "NORMAL" 
   sliceSize : "default" 
   machines : 
   machine : 
   ... 
   ... 
   cellDisks : "ALL" 
   diskGroupSize : "436G" 
   ocrVote : "true" 
   quorumDisk : "false" 
   id : "c0_dbfsdg" 
   version : "PhysicalLayoutLegacy" 
   diskGroupName : "DATAC1" 
   redundancy : "NORMAL" 
   sliceSize : "2953G" 
   machines : 
   .. 
   .. 
   cellDisks : "ALL" 
   diskGroupSize : "53154G" 
   ocrVote : "false" 
   quorumDisk : "false" 
   id : "c0_datadg" 
   version : "PhysicalLayoutLegacy" 
   diskGroupName : "RECOC1" 
   redundancy : "NORMAL" 
   sliceSize : "ALL" 
   machines : 
   .. 
   .. 
   cellDisks : "ALL" 
   diskGroupSize : "13284G" 
   ocrVote : "false" 
   quorumDisk : "false" 
   id : "c0_recodg"

3. Create an action for resizing the disk group.

   oedacli> ALTER DISKGROUP DISKGROUPSIZE='2500G' WHERE CLUSTERNUMBER=1 DISKGROUPN
   AME='DATAC1'

4. Save the action.

   oedacli> SAVE ACTION

5. Merge all actions.

   oedacli> MERGE ACTIONS
   processMerge 
   processMergeActions 
   Merging Action : alter diskgroup diskgroupsize='2500G' where diskgroupname='DAT
   AC1' clusternumber=1 
   Merging ALTER DISKGROUP
   Action Validated and Merged OK

6. Deploy the actions.

   oedacli> DEPLOY ACTIONS 
   Deploying Action ID : 3 alter diskgroup diskgroupsize='2500G' where diskgroupna
   me='DATAC1' 
   Deploying ALTER DISKGROUP 
   Deploying Action ID : 4 alter diskgroup diskgroupsize='2500G' where diskgroupna
   me='DATAC1' clusternumber=1 
   Deploying ALTER DISKGROUP 
   Validating ASM Disk status.. 
   Disks in ASM Disk Group DATAC1 have valid status 
   Shrinking Disk Group size to 2500 GB 
   Resizing ASM Disk Group.. 
   Checking Reblance operations in disk group DATAC1 
   Rebalance operations completed in disk group DATAC1 
   Original Grid Disk Size 2953 GB, new size 138 GB on node1celadm02.example.com 
   Original Grid Disk Size 2953 GB, new size 138 GB on node1celadm03.example.com 
   Original Grid Disk Size 2953 GB, new size 138 GB on node1celadm01.example.com 
   Updated/New Disk Group size 2484 GB, original size 53154 GB. 
   Done... 
   Done