My Oracle Support Banner

CLSRSC-180 - OPatchauto Fails Due To Old Entries In "crsconfig_params" File. (Doc ID 2570772.1)

Last updated on AUGUST 02, 2019

Applies to:

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

Symptoms

On : 12.2.0.1 version, Clusterware

opatch log.

---------------------------Patching Failed---------------------------------

Command execution failed during patching in home:<GRID_HOME>, host: Node 1.
Command failed: <GRID_HOME>/perl/bin/perl -I <GRID_HOME>/perl/lib -I <GRID_HOME>OPatch/auto/dbtmp/bootstrap_Node 1/patchwork/crs/install <GRID_HOME>/OPatch/auto/dbtmp/bootstrap_NODE1/patchwork/crs/install/rootcrs.pl -prepatch
Command failure output:

Using configuration parameter file:<GRID_HOME>/OPatch/auto/dbtmp/bootstrap_Node1/patchwork/crs/install/crsconfig_params
The log of current session can be found at:
  <ORACLE_BASE>/oracle/crsdata/Node1/crsconfig/crspatch_Node1_6_2019-07-22_12-52-12AM.log
2019/07/22 12:52:17 CLSRSC-180: An error occurred while executing the command 'cluutil -chkshare -oh <GRID_HOME> -localnode Node 1 -nodelist Node A,Node B'

 

 

OPatchauto taking the reference of old entries in the "crsconfig_params" file for Node name. Path to file: <GRID_HOME>/crs/install/crsconfig_params

"crsconfig_params.Node 2"

----------------------
INSTALL_NODE=Node B

HUB_NODE_LIST=Node A,Node B
NODE_NAME_LIST=Node A,Node B

 ----------------------

and

"crsconfig_params.Node 1"

----------------------
INSTALL_NODE=Node A

HUB_NODE_LIST=Node A,Node B
NODE_NAME_LIST=Node A,Node B

 ----------------------

 

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.