Exalogic: Exapatch Completes Successfully But With "WARNING: unable to update patch history: Unable to find unique identifier XXXXX for YYYYY nn.nn.nn.nnn in the rack history file." Message (Doc ID 2046822.1)

Last updated on NOVEMBER 14, 2022

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.1.1 and later
Linux x86-64
Oracle Solaris on x86-64 (64-bit)

Symptoms

You are running exapatch to patch a component of an Exalogic rack, such as the ilom of a specific compute node. Whilst the patching completes successfully and it's successful completion can be further validated by running /opt/exalogic.tools/tools/CheckHWnFWProfile, exapatch reports the following error while updating the rack_history.xml file (/exalogic-lcdata/inventory/rack_history.xml):

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

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

Exalogic: Exapatch Completes Successfully But With "WARNING: unable to update patch history: Unable to find unique identifier XXXXX for YYYYY nn.nn.nn.nnn in the rack history file." Message (Doc ID 2046822.1)

Applies to:

Symptoms

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!