ASM disk header corruption
Hi,
Calling all ASM experts - we have the problem described in note 1487443.1 . I have a simple question, as follows:
The affected diskgroups are shared by 4 databases, one on each of 4 servers in a cluster. These are all single-instance databases. One server in the cluster was shut down for some maintenance activity and, when it was restarted, some ASM diskgroups failed to mount, and subsequent investigation showed that we have the problem described above. The ASM instances on the other 3 servers are running correctly and have mounted the affected diskgroups.
My question is - do we have to shut down these other ASM instances (which would clearly affect the databases running on those servers) before implementing the fix described in the note? Any thoughts would be appreciated.
Calling all ASM experts - we have the problem described in note 1487443.1 . I have a simple question, as follows:
The affected diskgroups are shared by 4 databases, one on each of 4 servers in a cluster. These are all single-instance databases. One server in the cluster was shut down for some maintenance activity and, when it was restarted, some ASM diskgroups failed to mount, and subsequent investigation showed that we have the problem described above. The ASM instances on the other 3 servers are running correctly and have mounted the affected diskgroups.
My question is - do we have to shut down these other ASM instances (which would clearly affect the databases running on those servers) before implementing the fix described in the note? Any thoughts would be appreciated.
1