Creating an ASM Instance
ASM requires a dedicated Oracle instance to manage the disk groups. An ASM instance generally
has a smaller memory footprint, in the range of 60MB to 120MB, and is automatically configured
when ASM is specified as the database??™s file storage option when the Oracle software is installed
and an existing ASM instance does not already exist, as you can see in the Oracle Universal
Installer screen in Figure 4-18.
FIGURE 4-18 Specifying ASM as the database file storage method
100 Oracle Database 11g DBA Handbook
As an example of disk devices used to create ASM disk groups, suppose our Linux server has
a number of raw disk devices with the capacities listed in Table 4-2.
You configure the first disk group within the Oracle Universal Installer, as shown in Figure 4-19.
Device Name Capacity
/dev/raw/raw1 12GB
/dev/raw/raw2 12GB
/dev/raw/raw3 12GB
/dev/raw/raw4 12GB
/dev/raw/raw5 4GB
/dev/raw/raw6 4GB
/dev/raw/raw7 4GB
/dev/raw/raw8 4GB
TABLE 4-2 Raw Disks for ASM Disk Groups
FIGURE 4-19 Configuring the initial ASM disk group with OUI
Chapter 4: Physical Database Layouts and Storage Management 101
The name of the first disk group is DATA, and you will be using /dev/raw/raw1 and /dev/raw/
raw2 to create the normal redundancy disk group. If an insufficient number of raw disks are
selected for the desired redundancy level, OUI generates an error message. After the database
is created, both the regular instance and the ASM instance are started.
Pages:
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199