> Oracle 11gR2
> 2个故障组 – 正常的红色
>与单个磁盘关联的每个故障组
故障组Alpha是一个磁盘1,故障组Bravo在磁盘2上
我们最近在我们的一台Oracle服务器上遇到了一个问题.在Oracle运行时,我们的一个磁盘(我们称之为磁盘1 /故障组Alpha)失败了.当我们重新启动服务器时,Oracle不会出现,因为我们没有足够的磁盘来满足我们的冗余要求.
我们怎样才能从这次失败中恢复？
>有没有办法告诉Oracle启动失败组的实例,我们不在乎,我们将在以后修复磁盘问题？
>或者我们是否必须在实例重新启动之前弹出一个新磁盘？
这发生在我们的一个临时区域中,我们想了解将来可以做些什么…特别是如果没有备用磁盘.
ALTER DISKGROUP your_disk_group_name MOUNT FORCE
Mounting Disk Groups Using the FORCE Option
In the FORCE mode,ASM attempts to mount the disk group even if it cannot discover all of the devices that belong to the disk group. This setting is useful if some of the disks in a normal or high redundancy disk group became unavailable while the disk group was dismounted.
If ASM discovers all of the disks in the disk group,then MOUNT FORCE fails. Therefore,use the MOUNT FORCE setting only if some disks are unavailable. Otherwise,use NOFORCE [the default].
The disk group
mount succeeds if ASM finds at least one complete set of extents in a
disk group. If ASM determines that one or more disks are not
available,then ASM moves those disks off line and drops [sic!] the disks
after the DISK_REPAIR_TIME expires.In clustered ASM environments,if an ASM instance is not the first instance to mount the disk group,then using the MOUNT FORCE statement fails. This is because the disks have been accessed by another instance and the disks are not locally accessible.
