OCI-59033
failed to start Oracle ASM instance because it was unable to open SPFILE '%0!s'
Cause
An attempt to start the Oracle ASM instance failed because the ASM server parameter file (SPFILE) could not be opened. The SPFILE was configured in the indicated disk group. One or more of the disks in the disk group were inaccessible. This was likely due to the remote node or nodes being inactive.
Action
Issue the 'olsnodes' command to retrieve the list of nodes in the cluster. Start up all the remote nodes in the cluster that were previously inactive. Issue the 'crsctl start cluster' command on this node and verify that the Oracle ASM instance is active.
OCI-59033
failed to start Oracle ASM instance because it was unable to open SPFILE '%0!s'
Cause
An attempt to start the Oracle ASM instance failed because the ASM server parameter file (SPFILE) could not be opened. The SPFILE was configured in the indicated disk group. One or more of the disks in the disk group were inaccessible. This was likely due to the remote node or nodes being inactive.
Action
Issue the 'olsnodes' command to retrieve the list of nodes in the cluster. Start up all the remote nodes in the cluster that were previously inactive. Issue the 'crsctl start cluster' command on this node and verify that the Oracle ASM instance is active.
OCI-59033
failed to start Oracle ASM instance because it was unable to open SPFILE '%0!s'
Cause
An attempt to start the Oracle ASM instance failed because the ASM server parameter file (SPFILE) could not be opened. The SPFILE was configured in the indicated disk group. One or more of the disks in the disk group were inaccessible. This was likely due to the remote node or nodes being inactive.
Action
Issue the 'olsnodes' command to retrieve the list of nodes in the cluster. Start up all the remote nodes in the cluster that were previously inactive. Issue the 'crsctl start cluster' command on this node and verify that the Oracle ASM instance is active.
