Datasheet
54
Chapter 1
Using Oracle ASM
13. C. RBAL coordinates rebalance activity for a disk group in an ASM instance.
14. A. Note that the UNDROP operation will cancel a drop operation in progress but cannot
reverse a drop operation that has already completed. For HIGH REDUNDANCY, at least three
failure groups must be specified. While you can combine a drop and add operation into one
command, the command can reference only one disk group.
15. A. All types of database files are spread across all disks in the disk group to ensure redun-
dancy unless the redundancy is set to EXTERNAL.
16. A. If the DROP DISK operation has already completed, you must use ALTER DISKGROUP …
ADD DISK to add the disk back to the disk group. In any case, the disk group is continuously
available to all users and no data is lost.
17. A. The ADD DIRECTORY command is not likely to use V$ASM_OPERATION to track its prog-
ress, because this operation adds only a small amount of metadata—a directory object—to
the disk group and takes a minimal amount of time to complete. The V$ASM_OPERATION
view provides the status of long-running ASM operations.
18. D. The ALTER DISKGROUP … ADD DISK command adds all disks that match the discovery
string but are not already part of the same or another disk group.
19. E. The DISK_REPAIR_TIME attribute will prevent Oracle from automatically dropping the
disk in the disk group for a specific period of time. This gives you time to replace the con-
troller indicated in the question.
20. A, E. Apparently, for some reason DGROUP1 was not mounted when the ASM instance was
started, or the disk was missing and then reappeared (hardware failure perhaps) after the ASM
instance was started. ASM will discover new disks, even after the ASM instance is opened.
95134c01.indd 54 1/28/09 9:43:48 AM