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 220.127.116.11 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.
Grid Infrastructure "olsnodes" command shows deleted node as "Inactive Pinned":
<node1> Active Unpinned
<node2> Active Unpinned
<node3> Inactive Pinned
Attempted to unpin or delete but fails as well:
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
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