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

Listing 9-4. lst09-04-asm-disks.sql
SQL> select a.name,b.path
from v$asm_diskgroup a, v$asm_disk b
where a.group_number=b.group_number
and a.name='SDATA_CM01'
order by 2,1
/
Disk Group Disk
---------- ---------------------------------------------
SDATA_CM01 o/192.168.10.3/SDATA_CD_00_cm01cel01
SDATA_CM01 o/192.168.10.3/SDATA_CD_01_cm01cel01
... lines omitted for brevity
SDATA_CM01 o/192.168.10.4/SDATA_CD_00_cm01cel02
SDATA_CM01 o/192.168.10.4/SDATA_CD_01_cm01cel02
... lines omitted for brevity
SDATA_CM01 o/192.168.10.5/SDATA_CD_00_cm01cel03
SDATA_CM01 o/192.168.10.5/SDATA_CD_01_cm01cel03
... lines omitted for brevity
36 rows selected.
SQL>
From cellcli you can also determine which ASM disk group and ASM disk name is associated with your grid disks:
CellCLI> list griddisk where name like 'SDATA_.*' attributes name,asmDiskGroupName,asmDiskName
SDATA_CD_00_cm01cel01 SDATA_CM01 SDATA_CD_00_CM01CEL01
SDATA_CD_01_cm01cel01 SDATA_CM01 SDATA_CD_01_CM01CEL01
... Grid disks omitted for brevity
SDATA_CD_11_cm01cel01 SDATA_CM01 SDATA_CD_11_CM01CEL01
CellCLI>
While this example represents a typical Exadata disk group configuration in which disk groups contain disks spread
evenly across all storage servers, this practice is not required . You could build ASM disk groups on a subset of a storage
server's grid disks or even a subset of grid disks within your storage grid, using a script similar to that in Listing 9-5.
Listing 9-5. lst09-05-create_diskgroup.sql
SQL> create diskgroup SDATA_CM01
normal redundancy
failgroup cm01cel01
disk 'o/192.168.10.3/SDATA_CD_00_cm01cel01,
o/192.168.10.3/SDATA_CD_01_cm01cel01'
failgroup cm01ce0l2
disk 'o/192.168.10.4/SDATA_CD_00_cm01cel02,
o/192.168.10.4/SDATA_CD_01_cm01cel02'
attribute 'compatible.rdbms' = '11.2.0.3',
'compatible.asm' = '11.2.0.3.0',