My Oracle Support Banner

root.sh is failing on adding node with error "protocol error: filename does not match request :failed" (Doc ID 2710279.1)

Last updated on OCTOBER 19, 2020

Applies to:

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

Symptoms

root.sh is failing on adding node with error "protocol error: filename does not match request :failed"

Changes

Addition of the node is failing during running root.sh

rootcrs.log

2020-09-12 16:56:48: $GRID_HOME/bin/cluutil -sourcefile /etc/oracle/ocr.loc -sourcenode rac02 -destfile $GRID_HOME/srvm/admin/ocrloc
.tmp -nodelist rac02 ... failed
2020-09-12 16:56:48: capout=oracle.ops.mgmt.cluster.ClusterException: protocol error: filename does not match request :failed

2020-09-12 16:56:48: Running as user oracle: $GRID_HOME/bin/cluutil -sourcefile /etc/oracle/ocr.loc -sourcenode rac01 -destfile $GRID_HOME/srvm/admin/ocrloc.tmp -nodelist rac01
2020-09-12 16:56:48: s_run_as_user2: Running /bin/su oracle -c ' echo CLSRSC_START; $GRID_HOME/bin/cluutil -sourcefile /etc/oracle/ocr.loc -sourcenode
paappdb307 -destfile $GRID_HOME/srvm/admin/ocrloc.tmp -nodelist rac01 '
2020-09-12 16:56:49: Removing file /tmp/ibaQY2Me9
2020-09-12 16:56:49: Successfully removed file: /tmp/ibaQY2Me9
2020-09-12 16:56:49: pipe exit code: 256
2020-09-12 16:56:49: /bin/su exited with rc=1

 

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
References


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