Databases Reference
In-Depth Information
Chapter 9
Storage Administration
Understanding Exadata Storage Server architecture is one of the more important tasks for an Exadata administrator,
and an end-to-end knowledge of how storage “works” on Exadata is of critical importance. Chapters 1, 2, and 3
provided the foundation for the Exadata Storage Grid, and in this chapter, we'll cover some of the common
administration tasks as they relate to Exadata storage.
9-1. Building ASM Disk Groups on Exadata
Problem
You need to create one or more Oracle ASM disk groups on Exadata for Oracle database storage. In your non-Exadata
environments, you typically work with your storage administrator to identify candidate ASM disks or storage array
LUNs, but on Exadata, you're not sure where to find available storage or how to make free storage available for ASM
disk groups.
Solution
In this recipe, we will demonstrate how to identify Exadata grid disks using CellCLI commands and create Oracle ASM
disk groups on your Exadata grid disks.
Begin by using Exadata storage server
cellcli
commands to list existing grid disks and their sizes and pay
special attention to the disk prefix. I'll only display the first two lines:
[oracle@cm01dbm01 ~]$ dcli -g ./cell_group cellcli -e list griddisk attributes name,size
cm01cel01: DATA_CD_00_cm01cel01 284G
cm01cel01: DATA_CD_01_cm01cel01 284G
... Additional grid disk details omitted for brevity
The goal is to determine if you have available capacity on your Exadata cell disks to create new grid disks—at this
point, we may not want to actually do this depending on whether we already have ASM disk groups built on all of our
grid disks across all cells. Run another
cellcli
command and sort the output to show the unique grid disk sizes:
[oracle@cm01dbm01 ~]$ dcli -g ./cell_group cellcli -e list griddisk attributes name,size \
> | awk '{print $1, $3}'|sort -u
cm01cel01: 141G
cm01cel01: 284G
cm01cel01: 29.125G
cm01cel01: 36.6875G
cm01cel01: 67G
cm01cel02: 141G
Search WWH ::
Custom Search