Professional Documents
Culture Documents
Administering ASM DiskGroups With Exadata - Ebernal - Session PDF
Administering ASM DiskGroups With Exadata - Ebernal - Session PDF
Striping database files evenly across all available storage cells and disks
for optimal performance.
Using mirroring and failuregroups to avoid any single point of failure.
Enabling dynamic add and drop capability for nonintrusive cell and disk
allocation, deallocation, and reallocation.
Enabling multiple databases to share storage cells and disks.
PATH STATUS
------------------------------------------------------------ ------------
o/192.168.22.129:5042/data_CD_disk01_cell1 CANDIDATE
o/192.168.22.129:5042/data_CD_disk07_cell1 CANDIDATE
o/192.168.22.129:5042/data_CD_disk09_cell1 CANDIDATE
.
.
o/192.168.22.130:5042/data_CD_disk11_cell2 CANDIDATE
o/192.168.22.130:5042/data_CD_disk08_cell2 CANDIDATE
o/192.168.22.130:5042/data_CD_disk10_cell2 CANDIDATE
.
.
24 rows selected.
2 rows selected.
Note: Do not add Exadata Cell grid disks to a non-Exadata Cell ASM
diskgroup unless you are planning to migrate the diskgroup to an
Exadata Cell diskgroup.
When the disk is added, ASM will rebalance the diskgroup. You can query
the V$ASM_OPERATION view for the status of the rebalance operation.
Note: You can use the FORCE option of the ALTER DISKGROUP statement
MOUNT clause to mount diskgroups if their components are unavailable,
which results in a loss of full redundancy..
2. Use the SQL ALTER DISKGROUP statement with the OFFLINE DISK or
ONLINE DISK clause to change the disk in the ASM disk group to offline
or online:
SQL> ALTER DISKGROUP DATA OFFLINE DISK DATA_CD_DISK16_CELL1;
ASMDISK DISKGROUP
------------------------------ ------------------------------
DATA_CD_DISK12_CELL2 DATA
DATA_CD_DISK16_CELL1 DATA
DATA_CD_DISK04_CELL2 DATA
DATA_CD_DISK07_CELL2 DATA
2. Use the SQL ALTER DISKGROUP statement with the DROP DISK
clause to drop the disks from the ASM diskgroup:
SQL> ALTER DISKGROUP DATA DROP DISK DATA_CD_DISK16_CELL1;
Note: When the disk is dropped from the ASM diskgroup, ASM will
rebalance the diskgroup. You can query the V$ASM_OPERATION
view for the status of the rebalance operation.
SQL> SELECT * FROM V$ASM_OPERATION;
NAME STATE
------------------------------ -----------
DATA MOUNTED
2. Use the SQL DROP DISKGROUP statement to drop the ASM disk
group.
SQL> DROP DISKGROUP DATA;
Note: If you cannot mount a diskgroup but must drop it, you can use the
FORCE option of the DROP DISKGROUP statement:
SQL> DROP DISKGROUP DATA FORCE;
Zero downtime.
Requires ASM to be upgraded to release 11.1.0.7.
Necessity to use the rebalance POWER setting to control the effect on
applications.
NAME STATE
------------------------------ -----------
DATA MOUNTED
SQL> SELECT PATH, header_status STATUS FROM V$ASM_DISK WHERE path LIKE
'o/%' and STATUS like 'CANDIDATE' ;
PATH STATUS
------------------------------------------------------------ ------------
o/192.168.22.129:5042/data_CD_disk01_cell3 CANDIDATE
o/192.168.22.130:5042/data_CD_disk01_cell4 CANDIDATE
o/192.168.22.129:5042/data_CD_disk02_cell3 CANDIDATE
o/192.168.22.130:5042/data_CD_disk02_cell4 CANDIDATE
o/192.168.22.129:5042/data_CD_disk03_cell3 CANDIDATE
o/192.168.22.130:5042/data_CD_disk03_cell4 CANDIDATE
2 rows selected.
Note: When you alter the diskgroup to add Exadata Cell grid disks,
the cell.smart_scan_capable attribute must be set to FALSE.
FALSE
6. After the disk drop operation is completed, use the SQL ALTER
DISKGROUP statement to set the cell.smart_scan_capable disk group
attribute to be TRUE:
TRUE
The name of the grid disk should contain the cell disk name to make it easy to determine
which grid disks belong to a cell disk. To also help determine which grid disks belong
to an ASM diskgroup, a subset of the grid disk name should match all or part of the
name of the ASM disk group to which the grid disk will belong.
For example, if a grid disk is created on the cell disk CD_disk01_cell1 and that grid disk
will belong to an ASM diskgroup named DATA, then the grid disk name should
contain data_CD_disk01_cell1 and data. The grid disk name should be
data_CD_disk01_cell1.
PATH
----------------------------------------------------------------
o/192.168.22.129:5042/data_CD_disk01_cell1
Caution: Before changing the name of a grid disk that belongs to an ASM diskgroup,
ensure that the corresponding ASM disk is offline.
Note 1: When a grid disk in use by a database client is made inactive, then ASM
takes the corresponding ASM disk offline when I/Os to the disk fail. To make the
disk usable again, first make the grid disk active in the cell and then bring the
corresponding ASM disk back online in ASM.
Note 2: There is usually no need to change the grid disk state from active to inactive,
or from inactive to active. ASM will discover all active disks. However, if a grid
disk should not be available to ASM, then the grid disk should be changed to
inactive.
Note 3: If a diskgroup is created with external redundancy, and a grid disk in that
group is made inactive, then the diskgroup cannot be mounted.
data_CD_15_cell01,
data_CD_16_cell01;
ASMDISK DISKGROUP
------------------------------ -------------------------
DATA_CD_DISK12_CELL2 DATA
DATA_CD_DISK04_CELL2 DATA
DATA_CD_DISK07_CELL2 DATA
.
.