GPNP reports "gpnp call get-profile got invalid profile" error
(Doc ID 2985244.1)
Last updated on MAY 16, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.15.0.0.0 and laterLinux x86-64
Goal
There has been a requirement from our security team to ensure GPNP uses supported algorithms for signing.
The fix done in 21c and also included in 23ai, and it automatically signs the profile with the SHA512 at the end of upgrade if Grid Infrastructure (GI).
The fix is included in 19.16 GI RU (actually OCW RU) and is backported to 19.15. However this fix introduces an interoperability issue with 11.2.0.4 databases on those GI environment that is upgraded from an earlier GI version (i.e. 11g, 12c, and 18c).
The GPNP trace shows the following profile validation failure errors
2022-11-19 01:17:36.573: [ GPNP] clsgpnp_profileVerifyForCall: [at clsgpnp.c:1903] Result: (1) CLSGPNP_ERR. Profile failed to verify. prf=0xe774370
2022-11-19 01:17:36.573: [ GPNP] clsgpnp_profileCallUrlInt: [at clsgpnp.c:2209] Result: (0) CLSGPNP_OK. gpnp call get-profile got invalid profile 0xe774370. call discarded.
2022-11-19 01:17:36.574: [ CLSINET] failed to retrieve GPnP profile, grv 1
2022-11-19 01:17:36.573: [ GPNP] clsgpnp_profileVerifyForCall: [at clsgpnp.c:1903] Result: (1) CLSGPNP_ERR. Profile failed to verify. prf=0xe774370
2022-11-19 01:17:36.573: [ GPNP] clsgpnp_profileCallUrlInt: [at clsgpnp.c:2209] Result: (0) CLSGPNP_OK. gpnp call get-profile got invalid profile 0xe774370. call discarded.
2022-11-19 01:17:36.574: [ CLSINET] failed to retrieve GPnP profile, grv 1
Solution
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
| Goal |
| Solution |
| References |