My Oracle Support Banner

Stopping Clusterware on Second Node Blocks Disk Operations on <Node 1> For Several Minutes (Doc ID 2576717.1)

Last updated on SEPTEMBER 30, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Information in this document applies to any platform.

Symptoms

o On 12.2.0.1, on a 2-node cluster, the clusterware is stopped on the second node using 'crsctl stop crs'.

o Stopping the clusterware terminates the DB instance using 'shutdown abort', this is expected but also creates an orphan client entry in ASM.

o If an operation is performed on the ASM disks will take some time:  

 

o Issue is not reproduced on 18c or 19c.

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
Cause
Solution
References


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