Instances On Second Node Goes Down When Clusterware On First Node Stopped (Doc ID 3076943.1)

Last updated on MARCH 20, 2025

Applies to:

Oracle Database - Enterprise Edition - Version 19.25.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Instances on second node goes down when clusterware on first node stopped

All databases on the second node of a 2-node RAC cluster became unavailable after stopping the clusterware on the first node.
The 'ora.ASMNET1LSNR_ASM.lsnr' resource entered a PARTIAL online state during the evaluation of ASM connections, which caused the issue.

The following error was observed in the crsd_oraagent_grid.trc log:

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

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

Instances On Second Node Goes Down When Clusterware On First Node Stopped (Doc ID 3076943.1)

Applies to:

Symptoms

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!