odacli create-prepatchreport failed due to user mismatch (Doc ID 2939496.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database Appliance - Version All Versions and later
Information in this document applies to any platform.

Symptoms

For upgrading ODA to 19.13,odacli create-prepatchreport fails with the following error.

# odacli create-prepatchreport -s -v 19.13.0.0.0

...

# /opt/oracle/dcs/bin/odacli describe-prepatchreport -i <Job ID>

Patch pre-check report
------------------------------------------------------------------------
Job ID: <Job ID>
Description: Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER]
Status: FAILED
Created: March 22, 2023 3:19:35 AM JST
Result: One or more pre-checks failed for [GI]

Node Name
---------------
<Node0>

Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.13.0.0.0.
Is patch location available Success Patch location is available.
Verify OS patch Success Verified OS patch
Validate command execution Success Validated command execution

__ILOM__
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.13.0.0.0.
Is patch location available Success Patch location is available.
Checking Ilom patch Version Success Successfully verified the versions
Patch location validation Success Successfully validated location
Validate command execution Success Validated command execution

__GI__
Validate GI metadata Failed Metadata validation error <<<<<<<<<<<<<<
encountered: GI username mismatch <<<<<<<<<<<<<<
with DCS metadata, expected 'grid' <<<<<<<<<<<<<<
but found 'root'. <<<<<<<<<<<<<<
Validate supported GI versions Failed Internal error encountered: Failed to <<<<<<<<<<<<<<
run the opatch command : The user is <<<<<<<<<<<<<<
root. OPatch cannot continue if the <<<<<<<<<<<<<<
user is root. <<<<<<<<<<<<<<

OPatch failed with
error code 255.
Validate available space Success Validated free space under /u01
Is clusterware running Success Clusterware is running
Validate patching tag Success Validated patching tag: 19.13.0.0.0.
Is system provisioned Success Verified system is provisioned
Validate ASM in online Success ASM is online
Validate kernel log level Success Successfully validated the OS log
level
Validate minimum agent version Success GI patching enabled in current
DCSAGENT version
Validate Central Inventory Success oraInventory validation passed
Validate patching locks Success Validated patching locks
Validate clones location exist Failed Internal error encountered:
patchmetadata for 19.13.0.0.0 missing
target version for GI.
Validate DB start dependencies Success DBs START dependency check passed
Validate DB stop dependencies Success DBs STOP dependency check passed
Evaluate GI patching Failed Internal error encountered: Failed to <<<<<<<<<<<<<<
run the opatch command : The user is <<<<<<<<<<<<<<
root. OPatch cannot continue if the <<<<<<<<<<<<<<
user is root. <<<<<<<<<<<<<<

OPatch failed with
error code 255.
Validate command execution Success Validated command execution

__ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution

Node Name
---------------
<Node1>

OPatch failed with
error code 255.
Validate command execution Success Validated command execution

__ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution

Changes

upgrade ODA to 19.13

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

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

odacli create-prepatchreport failed due to user mismatch (Doc ID 2939496.1)

Applies to:

Symptoms

Changes

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!