SQL>
However, if disk space is tight, you don??™t need four members; for a high-redundancy disk
group, only three failure groups are necessary, so you drop the disk group and re-create it with
only three members:
SQL> drop diskgroup data2;
Diskgroup dropped.
If the disk group has any database objects other than disk group metadata, you have to specify
the including contents clause in the drop diskgroup command. This is an extra safeguard to make
sure that disk groups with database objects are not accidentally dropped. Here is the command:
SQL> create diskgroup data2 high redundancy
2 failgroup fg1 disk '/dev/raw/raw5' name d2a
3 failgroup fg2 disk '/dev/raw/raw6' name d2b
4 failgroup fg3 disk '/dev/raw/raw7' name d2c;
Diskgroup created.
SQL> select group_number, disk_number, name,
2 failgroup, create_date, path from v$asm_disk;
Chapter 4: Physical Database Layouts and Storage Management 111
GROUP_NUMBER DISK_NUMBER NAME FAILGROUP CREATE_DA PATH
------------ ----------- ---------- ---------- --------- ---------------
0 3 13-JUL-07 /dev/raw/raw8
3 2 D2C FG3 13-JUL-07 /dev/raw/raw7
3 1 D2B FG2 13-JUL-07 /dev/raw/raw6
3 0 D2A FG1 13-JUL-07 /dev/raw/raw5
2 1 RECOV_0001 RECOV_0001 08-JUL-07 /dev/raw/raw4
2 0 RECOV_0000 RECOV_0000 08-JUL-07 /dev/raw/raw3
1 1 DATA_0001 DATA_0001 08-JUL-07 /dev/raw/raw2
1 0 DATA_0000 DATA_0000 08-JUL-07 /dev/raw/raw1
8 rows selected.
SQL>
Now that the configuration of the new disk group has been completed, you can create a
tablespace in the new disk group from the database instance:
SQL> create tablespace users3 datafile '+DATA2';
Tablespace created.
Pages:
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215