My Oracle Support Banner

ODA: CRS cannot start on one ODA node if the other ODA node os shutdown (Doc ID 2652493.1)

Last updated on MAY 19, 2020

Applies to:

Oracle Database Appliance X7-2 HA Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X8-2HA Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Database - Enterprise Edition - Version 18.1.0.0.0 to 18.8.0.0.0 [Release 18]
Information in this document applies to any platform.

Symptoms

CRS failed to startup on 1st node after shudown the os of 2nd node,
even though the _disable_interface_checking=TRUE has been set.
below is the procedure to produce this problem:

1. Startup crs on both nodes.
2. Shutdown os on node2.
3. Stop crs on node1.
4. Start crs on node1, but crsd failed to start with bellow error.

# crsctl start crs -wait

Cluster Ready Service aborted due to Oracle Cluster Registry error
[PROC-44: Error in network address and interface operations Network address
and interface operations error [7]]. Details at (:CRSD00111:) in
/u01/app/grid/diag/crs/<host>/crs/trace/crsd.trc.
CRS-2883: Resource 'ora.crsd' failed during Clusterware stack start.
CRS-4406: Oracle High Availability Services synchronous start failed.
CRS-4000: Command Start failed, or completed with errors.

 

Due to this problem, if one side node of ODA X7-2 shutdown caused by OS/hardware issue,

then the surviving node's CRS will failed to restart.

Changes

ODA X7-2 HA 18.1 to 19.6

ODA X8-2 HA 18.1 to 19.6

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.