Potential disk corruption when adding a node to a cluster

(Doc ID 754594.1)

Last updated on FEBRUARY 28, 2014

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2 to 11.1]
Information in this document applies to any platform.
This problem can occur on any platform.


This problem can occur on any platform.

While adding a new node to the existing cluster, the root.sh on the new node hangs and the node addition fails.

The instances on the existing nodes encounters a corruption (e.g. ASM disk) and crashes. A restore of the asm disk is required to recover.


There are two situations where this can occur.

  1. On the new node that is to be added the voting disk or ocr disk location is incorrectly specified/mapped and in this example points to an active asm disk.
  2. On the original cluster, if the voting disk or ocr disk location has been changed in it's lifetime.

 * Other variations may also exist, in the sense it does not have to be only a problem with asm disks but other files and filesystems that is being pointed at.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms