CLSRSC-17: Invalid GPnP Setup during Postpatch
(Doc ID 2876938.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
After applying 19.14 GI patch, observed CLSRSC-17: Invalid GPnP setup messages observed during rootcrs.pl -postpatch
# $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/crs/install/rootcrs.pl -postpatch
Using configuration parameter file: /u01/app/19.0.0.0/grid/crs/install/crsconfig_params
The log of current session can be found at:
/u01/app/grid/crsdata/hostname/crsconfig/crs_postpatch_apply_inplace_hostname_2022-02-15_04-34-26PM.log
2022/02/15 16:34:37 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'
2022/02/15 16:35:09 CLSRSC-17: Invalid GPnP setup
Oracle Clusterware active version on the cluster is [19.0.0.0.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [3318786938].
2022/02/15 16:36:28 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.
2022/02/15 16:36:32 CLSRSC-672: Post-patch steps for patching GI home successfully completed.
The crs_postpatch_apply log will show
2022-02-15 16:35:09: ---> chk gpnp dir "/u01/app/19.0.0.0/grid/gpnp/gpnp_bcp__2020_7_8_18012" for cname=Cluster-c1, cguid=, pseq=
2022-02-15 16:35:09: /u01/app/19.0.0.0/grid/gpnp/gpnp_bcp__2020_7_8_18012/wallets/peer does not exist!
Changes
Customer renamed ClusterName="Cluster-c1" to "Cluster-c2" recently
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 |