which disks in the disk group will the new value be applicable?

You are managing an Oracle Database 11g ASM instance with a disk group dg01 having three
disks.
One of the disks in the disk group becomes unavailable because of power failure. You issued the
following command to change the DISK_REPAIR_TIME attribute from 3.6 hours to 5 hours:
ALTER DISKGROUP dg01 SET ATTRIBUTE *disk_repair_time’ = ‘5h’;
To which disks in the disk group will the new value be applicable?

You are managing an Oracle Database 11g ASM instance with a disk group dg01 having three
disks.
One of the disks in the disk group becomes unavailable because of power failure. You issued the
following command to change the DISK_REPAIR_TIME attribute from 3.6 hours to 5 hours:
ALTER DISKGROUP dg01 SET ATTRIBUTE *disk_repair_time’ = ‘5h’;
To which disks in the disk group will the new value be applicable?

A.
all disks in the disk group

B.
all disks that are currently in OFFLINE mode

C.
all disks that are not currently in OFFLINE mode

D.
all disks in the disk group only if all of them are ONLINE

Explanation:
Check out the answer options, it is tricky. The NOT OFFLINE disks equals ONLINE disks.
Refer to Set the DISK_REPAIR_TIME Disk Group Attribute Appropriately.
The DISK_REPAIR_TIME disk group attribute specifies how long a disk remains offline before
Oracle ASM drops the disk. If a disk is made available before the DISK_REPAIR_TIME parameter
has expired, the storage administrator can issue the ONLINE DISK command and Oracle ASM
resynchronizes the stale data from the mirror side. In Oracle Database 11g, the online disk
operation does not restart if there is a failure of the instance on which the disk is running. You
must reissue the command manually to bring the disk online.



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Magwai

Magwai

Altering the DISK_REPAIR_TIME attribute has no effect on offline disks. The new value is used for any disks that go offline after the attribute is updated. You can confirm this behavior by viewing the Oracle ASM alert log.