Storage Administration - Oracle Exadata Recipes: A Problem-Solution Approach - page 278

As you can see, our grid disks are 36.6875 GB in size and exist on each of three storage cells in our Exadata
Quarter Rack.

3. Drop your ASM disk group by connecting to an ASM instance as SYSASM :

[grid@cm01dbm01 ~]$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.3.0 Production on Thu Sep 13 16:25:10 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options

SQL> drop diskgroup sreco_cm01 including contents;

Diskgroup dropped.

SQL>

After this is complete, drop your grid disks using the cellcli command below: 4.

■ if you drop your exadata grid disks prior to dropping your aSm disk group, exadata's automatic disk manage-
ment features will automatically offline and drop your aSm disks.

Note

[oracle@cm01dbm01 ~]$ dcli -g ./cell_group cellcli -e \
> drop griddisk all prefix=SRECO
cm01cel01: GridDisk SRECO_CD_00_cm01cel01 successfully dropped
cm01cel01: GridDisk SRECO_CD_01_cm01cel01 successfully dropped
cm01cel01: GridDisk SRECO_CD_02_cm01cel01 successfully dropped
... output omitted
[oracle@cm01dbm01 ~]$

■ if your grid disks have aSm disk groups created on them that you neglected to drop, you can use the drop
griddisk [options] force syntax to forcibly drop your grid disks.

Note

Once the grid disks are dropped, recreate them using the create griddisk command via
cellcli :

5.

[oracle@cm01dbm01 ~]$ dcli -g ./cell_group cellcli -e create griddisk all \
> harddisk prefix='SRECO', size=36.6875G
cm01cel01: GridDisk SRECO_CD_00_cm01cel01 successfully created
cm01cel01: GridDisk SRECO_CD_01_cm01cel01 successfully created
cm01cel01: GridDisk SRECO_CD_02_cm01cel01 successfully created
... output omitted
cm01cel02: GridDisk SRECO_CD_00_cm01cel02 successfully created
cm01cel02: GridDisk SRECO_CD_01_cm01cel02 successfully created