Exadata Software - Oracle Exadata Recipes: A Problem-Solution Approach - page 45

Instance visx1 is running on node cm01dbm01
Instance visx2 is running on node cm01dbm02
[oracle@cm01dbm01 ~]$ nslookup cm01dbm01
sServer:

11.11.1.250

Address: 11.11.1.250#53

Name: cm01dbm01.centroid.com
Address: 172.16.1.10

[oracle@cm01dbm01 ~]$ nslookup cm01dbm02
Server:

11.11.1.250

Address: 11.11.1.250#53

Name: cm01dbm02.centroid.com
Address: 172.16.1.11

[oracle@cm01dbm01 ~]$

We know from Oracle documentation that database storage on Exadata is achieved solely using Oracle ASM, so
let's take a look at some of our tablespace data file storage:

SYS @ visx1> select tablespace_name,file_name
from dba_data_files
where rownum < 6
/

TABLESPACE_NAME FILE_NAME
-------------------- ------------------------------------------------------------
SYSTEM +DATA_CM01/visx/datafile/system.329.784250757
APPS_TS_TX_DATA +DATA_CM01/visx/datafile/apps_ts_tx_data.321.784250567
APPS_TS_TX_IDX +DATA_CM01/visx/datafile/apps_ts_tx_idx.378.784251053
UNDO_TBS +DATA_CM01/visx/datafile/undo_tbs.259.784250095
APPS_TS_NOLOGGING +DATA_CM01/visx/datafile/apps_ts_nologging.415.784251657

5 rows selected.

Our tablespaces are stored in an ASM disk group called DATA_CM01 . Let's examine the disks that make up this
ASM disk group:

SYS @ visx1> select a.name,b.path,b.state,a.type,b.failgroup
from v$asm_diskgroup a, v$asm_disk b
where a.group_number=b.group_number
and a.name='DATA_CM01'
order by 2,1
/

Disk Group Disk State TYPE Failgroup
---------- --------------------------------- ---------- ------ -----------
DATA_CM01 o/192.168.10.3/DATA_CD_00_cm01cel01 NORMAL NORMAL CM01CEL01
DATA_CM01 o/192.168.10.3/DATA_CD_01_cm01cel01 NORMAL NORMAL CM01CEL01
DATA_CM01 o/192.168.10.3/DATA_CD_02_cm01cel01 NORMAL NORMAL CM01CEL01