My Oracle Support Banner

CRS-4666: Could not find node <node name> to unpin (Doc ID 1970969.1)

Last updated on FEBRUARY 17, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Grid Infrastructure "olsnodes" command shows deleted node as "Inactive Pinned":

# olsnodes -s -t
<node1> Active Unpinned
<node2> Active Unpinned
<node3> Inactive Pinned

 

Attempted to unpin or delete but fails as well: 

# crsctl unpin css -n <node3>
CRS-4666: Could not find node <node3> to unpin.
CRS-4000: Command Unpin failed, or completed with errors.

 

If the scenario exists during upgrade, rootupgrade.sh fails:

Unable to create the directory "/u01/app/oracle" specified for diagnostic_dest parameter on nodes "<node3>". Make sure that the parent directory is writable and retry.

ASM rolling upgrade action failed, see logs for details

 

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.